Automate with Workflows / Lesson 9: Troubleshooting Workflow Errors
If your workflow encounters a technical error, a red error message will appear on the action that caused the issue and the workflow will automatically pause. This video will explain how to resolve a "too late to send" error, which is very common.
The too late to send error occurs when the time for an action to trigger has already passed. For example, in an event workflow you might send a questionnaire 12 months before the project start date. This will work correctly as long as the project start date is at least 12 months away when the workflow is applied. If you have a client book only 9 months in advance, you would see a too late to send error on any actions that would have needed to have already triggered in the past.
To resolve the error, click edit on the action and choose a new trigger, or set a fixed date at least five minutes in the future. Click apply to save the changes. Then click retry on the action. This option only appears when there has been an error, and you should only click it after correcting the cause of the error. After you click retry, refresh the page. You should no longer see the error message. Scroll to the bottom of the workflow and click paused to re-activate the workflow.
A too late to send error does not necessarily mean that your workflow was set up incorrectly. You may only run into this error on occasion with late-booking clients. If you do see this error frequently, re-assess the timing of the triggers in your workflow to better align with the timing of your process.
Tip #1
Reach out to chat support if an action is not running as you'd expect, even if you aren't seeing an error message. Do not remove actions or force actions in the affected workflow! Doing so will prevent our team from being able to diagnose the issue.
Tip #2
If you see an error you don't recognize, send us a chat! Our team is here to help.