FREE GOHIGHLEVEL TROUBLESHOOTING GUIDE
GoHighLevel workflows not triggering? Start here.
When an automation fails to run, resist the temptation to rebuild the entire workflow. First determine whether the contact entered the workflow, then find the first step that did not execute. The checks below help narrow down the cause.
Seven checks before you rebuild anything
- Check whether the workflow is published. Confirm the workflow is active rather than sitting in draft, and that you are inspecting the correct location/sub-account.
- Inspect the trigger. Does the event you expect actually match the selected trigger? A form submission, appointment booking and tag change are different events.
- Review trigger filters. Temporarily simplify restrictive filters in a safe test workflow. A filter that excludes your test contact can make a healthy workflow look broken.
- Check the contact's enrollment history. Look for evidence that the contact entered, was skipped or is waiting. The execution/enrollment view is more informative than guessing.
- Check re-entry settings. A contact that already entered may not be allowed to enter again. Review the workflow's re-entry rules before repeating the same test.
- Inspect waits, conditions and timing. A workflow can be working but waiting for a time window, a condition, or the next scheduled action. Confirm the account time zone and branches.
- Test one step at a time. Use a dedicated test contact and a reversible action. Note the trigger event, time, contact and first failed step. Avoid testing live campaigns on real customers.
Common failure patterns
The form was submitted, but nothing happened
Confirm the exact form or survey selected by the trigger, any filtering rules, and whether the test submission created or updated the contact you expected. Compare the form event time with the workflow history.
The contact entered, but no email arrived
That is not necessarily a trigger failure. Check whether the email action executed, whether a wait or condition held it, and whether the sending configuration and delivery logs show a problem. Do not assume inbox placement from a successful workflow step.
The workflow works once, then stops
Review re-entry rules, duplicate event behaviour and whether the contact already satisfies an exit or stop condition. Test with a new contact to isolate first-entry behaviour.
The wrong branch runs
Inspect the exact condition and the contact fields at the moment of evaluation. A field populated after the branch runs cannot affect a decision already made.
Frequently asked questions
Should I delete and recreate a broken workflow?
Usually not as the first step. Check publishing, trigger matching, filters and execution history before rebuilding. Recreating a workflow can obscure the original cause.
Does a successful workflow mean my emails reached the inbox?
No. Workflow execution and email deliverability are different checks. Review sending status and authentication separately.
Can an agency use this checklist for every client?
Use it as a starting point, but confirm the client's sub-account, trigger configuration and permissions. Test without exposing customer data or sending unintended messages.
Still spending too much time fixing workflows?
One broken automation is a troubleshooting task. Repeated client requests can become a support-capacity problem. Our free assessment helps you decide whether to improve your process or explore outside help.
Take the free support assessment → Explore free resources →
Independent educational guide, not official HighLevel documentation. Interfaces and feature names may change. Check current product guidance before applying changes to a live client account.