Start here: did the contact enter the workflow at all?
Before changing anything, find out whether the workflow did not start or started and then stopped. They have different causes.
- Open the workflow and go to the Enrollment History tab. If your test contact is not there, the trigger never fired: check items 1 to 5 below.
- If the contact is there, open the Execution Logs tab and click the contact. You will see each step and where it stopped or skipped: check items 6 to 10.
1. The workflow is still in Draft
Workflows only run when the toggle at the top right is set to Publish and the changes are saved. Editing a published workflow and leaving without saving keeps the old version running.
2. The trigger filters do not match
Click the trigger and read every filter. Common mistakes:
- A Form Submitted trigger filtered to a different form, or an old copy of the form.
- A Tag Added trigger looking for a tag that is spelled slightly differently (tags are matched exactly).
- An Appointment trigger filtered to one calendar while bookings go to another.
- A Pipeline Stage Changed trigger filtered to the wrong pipeline.
Remove filters one at a time while testing to find the one that blocks enrollment.
3. The event happened in a way the trigger does not catch
Triggers react to specific events. For example, Contact Created does not fire when an existing contact fills in a form again, and a tag added by an import may not behave like a tag added manually. Test with the exact real-world action: submit the real form, book through the real calendar link, move a real opportunity.
Rather have an expert look at it?
FREEGet a free account health check4. Re-entry is turned off
By default a contact can only go through a workflow once. If you are testing with the same contact again, it will be skipped. In the workflow Settings, turn on Allow re-entry if contacts should be able to repeat it, or test with a new contact.
5. Another workflow removed the contact first
A Remove from workflow action, or a "Remove from all workflows" option in another automation, can pull the contact out instantly. Search your other workflows for remove actions that target this one.
6. The contact has DND (Do Not Disturb) on
If the contact has DND enabled for all channels or for SMS or email, those message steps are skipped even though the workflow runs. Check the contact record. Contacts who replied STOP are automatically set to DND for SMS.
7. A wait step or time window is holding the contact
Wait steps, "wait until" conditions and the workflow's time window setting (for example, only send between 9am and 5pm) all pause contacts. The execution log shows "waiting". Check the workflow's time zone too: the sub-account time zone and the contact's time zone can differ.
8. An If/Else branch sent the contact the other way
The execution log shows which branch the contact took. If it went down the wrong path, check the condition: custom field values must match exactly, and empty fields often fall into the "None" branch.
9. The message step failed to send
If the log shows the step ran but nothing arrived, the problem is the channel, not the workflow:
- SMS: no A2P 10DLC approval on US numbers, the contact's phone number formatted wrongly, or carrier filtering. See our guide on fixing A2P rejections.
- Email: no dedicated sending domain, or missing SPF, DKIM and DMARC records, so messages go to spam or bounce.
10. A goal event or "stop on response" ended it early
Goal events (such as "Appointment booked") and the Stop on response setting end the workflow for a contact as soon as the goal is met or the contact replies. That is usually intended, but it surprises people during testing.
How to test a workflow properly
- Create a fresh test contact with your own email and phone number.
- Trigger the workflow with the real action (real form, real calendar, real pipeline move).
- Temporarily shorten long wait steps while testing, then put them back.
- Check Enrollment History and Execution Logs after each test.
- Delete the test contact or tag it so it does not count in reports.