Guide, troubleshooting

GoHighLevel workflow not triggering: a diagnostic path

When a GoHighLevel workflow does not trigger, check in this order. Confirm it is published. Open Stats View to see whether the trigger is matching. Compare the record against each filter. Check Allow Re-entry. Then read Enrollment History and Execution Logs to find out whether the contact entered and which step failed.

Last updated November 1, 2026

Step 1: Is the workflow published?

Draft workflows do not trigger or act. Check this first, because it takes seconds.

Step 2: What does Stats View show?

Step 3: Is it the right trigger?

Make sure the event happens in this sub-account and that you picked the trigger for that event. A form trigger will not fire for a survey, for example. Trigger the event once yourself while watching the counts.

Step 4: Which filter is rejecting the record?

Compare the actual record against every filter, one at a time. Remove filters until it matches, then add them back. The last one you add is the culprit.

Step 5: Is re-entry blocking it?

This is the most common cause on call-based workflows. Allow Re-entry decides whether a contact can enter again, and even then a contact can only re-enter after finishing the workflow or being removed. HighLevel notes that appointment and invoice triggers bypass the setting.

Test with a fresh contact to rule out earlier enrollment.

Step 6: Which step failed?

Open Enrollment History and Execution Logs for that contact. They show whether any later step was skipped or failed. For SMS steps, check A2P registration next. For steps that depend on a connection, check whether the connection survived a snapshot import.

When should you stop and ask for help?

When several workflows contact the same person, or when nobody knows why a workflow exists. Tracing that kind of account is the job. It comes out of prepaid hours, and we scope it first.