GoHighLevel workflow not triggering? How to find the cause and fix it

First, work out which problem you have

Before you change anything, pick one contact who should have gone through the workflow but did not. What happened to that contact usually points straight at the cause.

A word on testing. The Test Workflow button in the top right of the builder lets you pick a contact and click Run Test, but HighLevel's builder walkthrough says testing this way "isn't 100% perfect" and recommends publishing the workflow and testing it live. Its troubleshooting steps also suggest testing with a fresh contact that has never been in the workflow, so earlier enrolments and re-entry rules don't confuse the result.

Fix 1: Make sure the workflow is published and saved

This is the quickest thing to check, and the usual culprit right after someone has edited a client's automation.

1. In the client's sub-account, go to Automations, then Workflows, and open the workflow.
2. Find the Draft/Publish toggle in the top-right corner. A workflow in Draft does not run for real. Switch it to Publish.
3. Check the Save button next to it. A red dot means there are unsaved changes, so click Save.

HighLevel treats saved and published as separate states. A workflow can be published while your latest edits are still unsaved, or saved while it is still in Draft. When you switch a draft workflow back on, contacts who were on a waiting step stay where they were. If HighLevel won't let you publish, go straight to Fix 2.

Check it worked: trigger the event with a fresh test contact (submit the form or add the tag), then open the workflow's Enrollment History. The contact should be listed there.

Fix 2: Clear anything flagged in the Resolve Errors panel

HighLevel checks triggers and actions for problems it can detect and marks the affected step with an error indicator. Its article on highlighting and resolving errors describes the steps.

1. Select Review issues to open the Resolve Errors sidebar, which lists every affected trigger and action.
2. For each item, click Open step to go to it and correct the setting, or How to fix for AI-assisted guidance. Read any suggested change before you accept it.
3. Save, then publish.

Typical things it flags: required fields left empty, selections that are missing or invalid, integrations that are disconnected or unavailable, and If/Else or Wait steps that are set up wrongly. You can save a workflow that has errors, but publishing stops with a Workflow can't be published yet message that lists what needs fixing.

Two caveats. A workflow that is already published does not go back to Draft if an error turns up later, so a live workflow can have a broken step without anyone noticing. HighLevel also says its error checking does not yet cover everything, so an empty panel does not prove the workflow is right.

Check it worked: the indicators clear on their own once a problem is fixed, and the workflow publishes without the warning.

Fix 3: Check the trigger and its filters

If some contacts enter and others don't, the trigger is usually doing exactly what it was told. Open the trigger at the top of the workflow and compare every filter with the record of the contact who was missed.

• Form Submitted: the Form Is filter must name the form the visitor actually filled in. If a form was copied for a new landing page, the workflow may still point at the original. HighLevel's Form Submitted trigger article says the trigger works with forms built inside HighLevel. Forms from outside tools may need an integration or a webhook.
• Contact Tag: the trigger fires when a tag is either Added or Removed, so check it is set to the one you need and that the tag name matches exactly. The Contact Tag trigger article notes that the workflow fires only after the tag change has actually been applied, and only for tags added or removed after the workflow is active.
• Several tag filters on one trigger: the Contact Created trigger article says multiple tag filters combine with AND logic, so the contact must match all of them. A "Not equals to" or "None of" filter can quietly exclude the very contact you are testing with.
• Contact Created: the same article says bulk imports do not trigger this workflow, and a contact merged into an existing record will not trigger it again.

Also check whether other workflows in the sub-account use the same trigger. HighLevel says all workflows with the same trigger fire at the same time, and it suggests avoiding that kind of overlap.

Check it worked: create a fresh contact that meets every filter, trigger the event, and confirm the contact shows up in Enrollment History.

Fix 4: Check Allow Re-entry and the other contact settings

If the workflow ran for a contact once and now ignores them, a setting is the likely reason. Open the workflow and click the Settings tab at the top of the page. The options are under Contact Settings, as described in HighLevel's workflow settings overview.

• Allow Re-entry: when it is off (grey), a contact can enter and complete the workflow only once. When it is on (blue), a contact can enter again after fully completing the workflow or being removed manually. Even with it on, a contact who is still active in the workflow cannot re-enter.
• The exception: workflows with an appointment or invoice-based trigger always let a contact enter once per appointment or invoice, whatever this toggle says.
• Allow multiple Opportunities: when it is off, only the first opportunity that meets the trigger criteria enters the workflow. It is on by default for new workflows but off for workflows created before the feature existed, so check older client workflows that run on opportunities.
• Stop on Response: when it is on, the workflow ends for any contact who replies to a message sent from that workflow. It can look as though the automation stopped halfway, when it actually did what it was set to do.

Save and publish after any change.

Check it worked: trigger the event again for a contact who has already completed the workflow. With re-entry on, they should appear in Enrollment History a second time.

Fix 5: Read Enrollment History and Execution Logs

When the setup looks right, the logs show what really happened. HighLevel's article on execution logs and enrollment history covers both.

1. Go to Automations, then Workflows, open the workflow and click Execution Logs. Enrollment History is right next to it.
2. Set the date range to cover the event: a preset such as Today or Yesterday, or a custom range of up to 30 days.
3. If a message was involved, there is a quicker route. Open the conversation in Conversations, open the message details and click the workflow link under Workflow. Execution Logs opens with that contact and run already selected.

What the results mean:

• The contact is not in Enrollment History at all: the trigger never fired for them. Go back to Fix 1 and Fix 3.
• Workflow Completed, Removed by Workflow Action or Removed by External Workflow Action: in order, these mean the contact finished normally, a step in this workflow removed them, or a step in a different workflow removed them. If you see the last one, look through the client's other workflows.
• Removed by - Snapshot Refresh: a snapshot refresh deleted the contact's waiting step. Agencies that push snapshot updates to client accounts should look out for this one. Open the entry to see the details in the side panel.
• A highlighted Status or View Details link: an action hit an error. Open the details, then use Go To Action to jump to that step in the builder.
• Not sure where the contact went: click the Highlight Contact Path icon. The builder opens with the contact's route marked, including steps that errored and steps that were skipped.
• An action shows as successful but nothing changed on the contact: check the timestamps. If two actions ran in the same second, HighLevel calls this a race condition and recommends adding a Wait action of 1 minute between them.
• A text or email is waiting rather than failed: look at Time Window under Communication Settings in the Settings tab. Messages scheduled outside the window pause and go out at the next available time. Internal actions such as adding tags or updating fields are not affected.

Check it worked: run a fresh contact through, then use Highlight Contact Path to confirm there are no error steps and nothing was skipped unexpectedly.

If none of this worked

Gather the evidence before you contact support. It saves a round of questions, and HighLevel's own troubleshooting steps ask for much the same.

• The sub-account name and the exact workflow name
• The affected contact (name plus email or phone)
• Roughly when the event happened, and in which timezone
• What should have happened, and what actually happened
• Screenshots of the trigger and its filters, the Settings tab, and the Enrollment History and Execution Logs entries with View Details open

According to HighLevel's support options article, only Agency Admins and Agency Users can see the support button, so if you are the client, send all this to your agency. From an agency login, click the blue question mark in the top-right corner (desktop only) to start a live chat with AI Support Chat or Agent Chat. Chats that aren't resolved become a ticket. You can also join the Zoom queue or open a ticket directly. There is no general support email address, and the phone line is for sales, billing and login issues, so use chat or a ticket for workflow problems.

Frequently asked questions

Why does my workflow work with Test Workflow but not with real contacts?

HighLevel says testing with a contact inside the builder is not 100% perfect and recommends publishing the workflow and testing it live. Use a fresh contact that has never been in the workflow, then compare the real event (which form, which tag) with the trigger filters.

Will a newly published workflow pick up contacts who already had the tag?

No. HighLevel says tags trigger workflows only when they are added or removed after the workflow is active. To enrol existing contacts, filter them in Contacts, then Smart Lists, select them and use Trigger automation to add them to the workflow. Only published workflows appear in that list.

The log says Add Tag succeeded, so why is the tag missing from the contact?

HighLevel describes this as a race condition: two updates in the same second can land out of order. Check the timestamps in Execution Logs, then add a Wait action of 1 minute between the two actions.

What does 'Removed by - Snapshot Refresh' mean in the logs?

It means a snapshot refresh deleted the contact's waiting step, so they left the workflow at that point. Open the entry in Execution Logs to see the details in the side panel, then decide whether those contacts need adding back, keeping your Allow Re-entry setting in mind.

Can my client contact HighLevel support about this directly?

Usually not. HighLevel says only Agency Admins and Agency Users see the support button, and location admins and users do not. Clients should send the details to their agency, which can raise it through live chat or a ticket.

When the follow-up should live with the website

Usually one of the fixes above is enough, and there's no reason to move. But if you are rebuilding a client's site anyway and want the form, the contacts and the follow-up all in one place, WebNewBiz runs trigger-based workflow automations (for example on a form submission, a scheduled date or a birthday) inside the same CRM as the website. That comes with Growth ($79 a month) and above, and website enquiries land in the CRM automatically. The honest limits: it is a younger platform with a smaller ecosystem than GoHighLevel's agency programme, the CRM is not included on the cheaper Lite and Starter plans, and agency pricing is not published. Create your website for $1, or if you run an agency, talk to us about white-label. If you are comparing options more widely, see our guide to GoHighLevel alternatives.