When a notification is selected in the Timesheet Workflow, notification emails are automatically sent from FastTrack360 based on the notification settings. Notification emails may be delivered late, or not at all if the email was treated as spam.
In order to check if a notification has been successfully generated and sent from FastTrack360, the following checks should be made. Its important that the checks are made in the order outlined below.
To generate a notification email, a notification must be selected in the Timesheet Workflow.
If no selection has been made, select the relevant notification for it to apply to future Timesheets. |
Once selected in the Timesheet Workflow, emails are generated based on the notification settings.
Timesheet Workflow Stage notification is used | Type | Trigger | Grouping | Delivery Frequency | When notification should send |
---|---|---|---|---|---|
Approval Levels | Immediate | Submitted | None | NA | Once timesheet is submitted |
Initiator | Immediate | Approved | 3 hours | NA | Next 3 hour interval after the timesheet was submitted |
Initiator | Scheduled | Reminder | None | -56 hours | 56 hours before midnight of the timesheet week ending date |
Approval Levels | Scheduled | Reminder | None | 14 hours | 14 hours after the timesheet was submitted |
Grouping intervals are based on a 24 hour period so a 3 hour interval will send notifications at 03:00, 06:00, 09:00, 12:00, 15:00, 18:00, 21:00, 24:00. The Communication Service runs every 5 minutes. Once a notification is ready to send, it will be sent the next time the service is run. |
Refer to Creating Notifications for further details.
Once you've determined a notification email should have generated, the Communication History will show if it has been sent from FastTrack360
If the notification doesn't appear in the Communication History, please have your FastTrack Administrator (FTA) lodge a request via our Service Desk portal and provide the following details for each notification that wasn’t received:
Notification emails appearing in the Communication History have been sent from FastTrack360 however they may not have been received in the recipients Inbox or may be received later than expected due to:
If only the IP address, 13.55.19.10/32, has been added to your SPF record, delays will still occur. Your SPF record must also have “include:spf.messagelabs.com ~all” to ensure emails sent from FastTrack360 aren't treated as spam. |
If the email isn’t in the Spam/Junk folder and your SPF record has been updated with FastTrack's details but you are still experiencing issues with notifications not being received, please have your FastTrack Administrator (FTA) lodge a request via our Service Desk portal and provide the following details for each notification that wasn’t received:
Related articles appear here based on the labels you select. Click to edit the macro and add or change labels.
|