Why didn't my workflow run?
Open the workflow and read Run history. Each run has a status and a timeline of what already happened.
Check these first
- The workflow is turned on. A paused workflow does not start from a new submission.
- It is watching the form that was submitted.
- An if/else filter may have taken a path with no further steps. That still counts as a completed run.
- An email step is skipped when there is no recipient, for example a respondent email field is empty.
- SMS and WhatsApp actions are not available yet, so those steps are skipped.
- Approval and delay steps are not available yet, so those steps are skipped and the run continues.
Run history
Open the workflow. Run history lists recent runs with a status: running, waiting, completed, failed, or cancelled. Open Details for the timeline: started, each step, skipped, waiting, reminded, completed, failed, or expired.
You can filter the list to failed runs. Waiting usually means the person has not submitted the next form yet, or an approval or delay is parked (those last two are not available yet).
Test without sending
Test without sending is not available yet. When it ships, you can pick a past submission and run the saved steps. No emails, webhooks, integrations, SMS, approval requests, or next-form links are sent, and status changes are not applied. Delay steps are logged as “would wait” and the run continues so later steps can be previewed. Approval and send-next-form steps stop the test run. Paused workflows can still be tested. Test runs are labelled Test and do not block a later live run of the same submission.
Safety caps
Safety caps (how many steps a run can take, how many workflows can be on for one form, and how fast runs and emails go out) are not available yet. When they ship, runs over a cap start a little later instead of being dropped, and when a cap skips a run or a step, run history says so. Caps are not tied to a plan, and there is no upgrade prompt.
Retry a failed run
Retry is not available yet. When it ships, failed runs get a Retry button that restarts from the failed step. Earlier steps do not run again. A retry skips a step that already sent, which reduces duplicate emails and other side effects. That skip is best-effort. Do not treat Retry as a promise that nothing will ever send twice.