Short answer
A GoHighLevel workflow usually fails to trigger because the workflow is unpublished, the trigger filters do not match the contact, Allow Re-entry is off, or the opportunity settings skip the contact. Open Trigger Stats first. It shows who was attempted, who matched, and the reason for each unmatched contact.
In this post
- Start with the evidence
- Cause 1: The workflow is not published
- Cause 2: Trigger filters do not match
- Cause 3: Allow Re-entry is off
- Cause 4: Opportunity settings skip the contact
- Cause 5: The workflow stopped for the contact
- Cause 6: A time window is pausing actions
- Cause 7: A person changed the account
- A short debugging order
Start with the evidence
Before you change anything, look at what the workflow recorded. Three views tell you most of what you need.
- Trigger Stats shows three counts: Attempted (contacts the trigger evaluated), Matched (contacts that met every condition) and Unmatched. Click a count to open the panel, which lists each contact with a “Reason for Unmatch”, such as a value mismatch or a missing field. Stats update in real time and are kept for the last 30 days.
- Enrolment History shows how each contact left: Workflow Completed, Removed by Workflow Action, or Removed by External Workflow Action.
- Execution Logs list each action with its time and a View Details link. Errors are highlighted. In the builder, Highlight Contact Path shows the route a contact took, including skipped nodes and errors.
Zero attempted contacts points to the trigger or the publish state. Attempted but unmatched points to filters. Matched but no action points to settings or the actions themselves.
Cause 1: The workflow is not published
GoHighLevel’s own troubleshooting tip for workflows that create opportunities starts with confirming the workflow is published. Check it first. A draft never runs.
Cause 2: Trigger filters do not match
The common causes in GoHighLevel’s trigger FAQ are a wrong value, a missing field, or the wrong trigger selected. A form trigger that filters on one form name will not fire for a second form with a similar name. Compare the trigger setup with the contact record. Use the Unmatch reason to see which condition failed.
Cause 3: Allow Re-entry is off
With Allow Re-entry on, a contact can enter again after finishing or after a manual removal. They cannot re-enter while still active. With it off, a contact can enter and finish the workflow only once. Appointment-based and invoice-based triggers always allow re-entry for each new appointment or invoice, whatever the setting.
GoHighLevel changed the default so that new workflows have Allow Re-entry on. Older workflows were not changed, so a workflow built long ago may still have it off. Check the Settings tab of any workflow where repeat contacts fail to enter.
Cause 4: Opportunity settings skip the contact
Opportunity triggers have two settings worth checking.
- Allow multiple opportunities. With it off, only the contact’s most recent opportunity enters the workflow, and updates to an older opportunity skip the remaining actions. With it on, each opportunity runs as its own execution. It is on by default for new workflows and off for workflows created before the feature launched. Updating an opportunity does not restart its workflow.
- Allow Opportunity to Move. If an opportunity will not change stage through a workflow, check this setting on the action.
Cause 5: The workflow stopped for the contact
Stop on Response removes a contact when they reply to a message sent by the workflow. This is by design, and it affects only that contact. If the contact never reaches later steps, check whether a reply, including a voicemail with voicemail detection off, ended the run.
Cause 6: A time window is pausing actions
The Time Window setting limits SMS, email and calls to the hours and days you choose. An action outside the window pauses and resumes at the next slot. It does not affect internal actions such as tags, field updates or opportunities. If texts seem missing, check the window before assuming a failure.
Cause 7: A person changed the account
A snapshot refresh that deletes a step can remove contacts waiting on that step. The execution log shows “Removed by – Snapshot Refresh”. Contact merges also change in-progress runs, and the log records a Contact Merge entry.
A short debugging order
- Confirm the workflow is published.
- Open Trigger Stats and read the unmatched reasons.
- Check Allow Re-entry and the opportunity settings.
- Read the enrolment history and execution log for the contact.
- Check Stop on Response and the Time Window.
- Test with a fresh contact that meets every filter.
If the log shows nothing and the cause stays unclear, that is a good moment for an audit. A second pair of eyes finds in an hour what the workflow’s own owner has looked past for a week.
Sources: GoHighLevel Help: “Workflow Settings – Overview”; “Trigger Narration and Statistics”; “Improved Workflow Execution Logs & Enrollment History”; “Multiple Opportunities Toggle in Workflows”; “Getting Started – Setup Pipelines and Opportunities”; GoHighLevel Ideas: “Allow Re-Entry Default Setting changes”.
Want this set up for you?
30 minutes, a clear next step.
Anis Mahmud Anik
HighLevel Certified Admin. I set up and automate GoHighLevel for founders and owners.



