GoHighLevel workflow not triggering? Causes and fixes

By / Published Nov 11, 2026 / Updated Nov 11, 2026

Heads up: the trial and plan buttons on this page use my affiliate links. If you sign up through one I get a commission. It doesn't cost you more.

A GoHighLevel workflow that isn't triggering is almost always one of five things: it's still in Draft, the contact didn't match every trigger filter, re-entry is off and they've been through it before, the contact is on DND so the message step can't send, or two steps raced each other in the same second. Open the workflow, turn on Stats View to see if the trigger matched the contact, then read Execution Logs and Enrollment History for that contact, and you'll know which one it is in a couple of minutes.

I run my agency on GoHighLevel, and the fix is rarely clever. It's knowing where to look. Below is the checklist I'd run first, then each cause with the symptom, the exact place to confirm it and the fix, a symptom to cause table, and the new tools for inherited accounts: Workflow Maps (Oct 27, 2026) and Workflow AI Analytics (Nov 9, 2026). If you're still learning how workflows fit together, start with GoHighLevel workflows.

Start your 30-day free trial →

30 days free instead of HighLevel's usual 14, plus a 1:1 setup call with my team, weekly live calls and my agency resources from day one. See everything you get →

Short version

  • 01Draft workflows don't run. Saving isn't publishing: check the Draft/Publish toggle top right.
  • 02Stats View (top left of the builder) shows Attempted, Matched and Unmatched for the trigger. Unmatched means a filter didn't fit, and you can click in to see why.
  • 03Re-entry off blocks anyone who's been through before. Test with a brand new contact, which is HighLevel's own first tip.
  • 04DND doesn't stop a contact entering. It stops the message steps for that channel, and carriers can switch it on by themselves.
  • 05Two steps in the same second can race. HighLevel's fix is a 1-minute Wait between them.
  • 06For an account you didn't build: Automation > Workflows > Workflow Maps > Review workflows with errors, then trace the contact.

The 2-minute diagnostic checklist

  1. 01

    Is it published?

    Open the workflow and look at the Draft/Publish toggle top right. HighLevel's builder doc is blunt: Draft mode "will not trigger and take actions for real". Save and Publish are separate, so a saved workflow can still be a draft. If Publish is blocked, you'll get a "Workflow can't be published yet" box: click Review issues and fix what it lists.

  2. 02

    Did the trigger match the contact?

    Turn on Stats View (top left of the builder) and click the trigger. Attempted is everyone it checked, Matched is who got in, Unmatched is who didn't fit the filters. Click Unmatched, search the contact, and it shows why. It covers the last 30 days, and you can't edit while Stats View is on.

  3. 03

    Have they been through it before?

    Settings tab > Allow Re-entry. Off means once, ever. On still won't let someone in while they're active in it. Your test contact from last week is the usual victim, so test with a fresh contact.

  4. 04

    Is the contact on DND?

    Open the contact and check the DND section at the bottom of the left column. A channel on DND means that step won't send, even though the workflow ran.

  5. 05

    What do the logs say?

    Execution Logs (top of the workflow) shows every action per contact with errors highlighted. Enrollment History shows whether they finished, were removed by this workflow, or were removed by another one. Click Highlight Contact Path to see their route on the canvas, with skipped steps and errors marked.

  6. 06

    Still stuck? Ask Workflow AI

    Since Nov 9, 2026: open the workflow, click the Workflow AI icon in the left bar, open the Chat tab and ask "Show me the path [contact name] took through this workflow." It answers step by step with times and outcomes, flags repeat enrollments, and can follow the same contact across every workflow in the account.

Symptom to cause: find your problem fast

Match what you're seeing to the likely cause, then jump to that section below.

What you seeMost likely causeWhere to confirm
Nobody enters, everWorkflow is a draft, or the trigger is set to the wrong form, calendar or tagDraft/Publish toggle; Stats View on the trigger
Some contacts enter, others don'tA trigger filter doesn't fit those contactsStats View > Unmatched > search the contact
Worked once, not the second timeAllow Re-entry is off, or they're still in the workflowSettings tab; Enrollment History
Contact entered but no text or email arrivedDND on that channel, an SMS failure, or the Time Window is holding itContact's DND section; Execution Logs; the conversation
Log says "tag added" but the contact has no tagRace condition: two steps fired in the same secondExecution Logs timestamps
Contact left halfway throughStop on Response, a goal, or another workflow removed themEnrollment History status
Same person got the message twiceTwo workflows on the same trigger, or duplicate contactsWorkflow Maps contact trace; Contacts > Manage Duplicates
Contact stuck on a Wait foreverWait condition never met, or the wait was set before you edited itExecution Logs; Highlight Contact Path
Webhook, Slack or Facebook step failsDisconnected integration or bad endpointWorkflow Maps > Review workflows with errors
Old tagged contacts never enteredTriggers don't fire backwardsAdd them by hand or with a bulk action

Built from HighLevel's workflow help docs and changelog, read Nov 11, 2026.

Cause 1: the workflow is still a draft (or can't be published)

Symptom: nothing happens for anyone. Confirm: open Automation > Workflows, open the workflow and read the toggle top right. Fix: switch it to Publish and save.

HighLevel now won't let you publish a workflow with certain setup errors. You can still save it, so it sits in Draft looking finished. When you click Publish you get a "Workflow can't be published yet" box. Click Review issues, then use Open step to jump to each broken trigger or action, or How to fix for an AI explanation. Typical ones from HighLevel's doc: an appointment trigger with no calendar picked, an SMS with an empty body, an email with no subject, a disconnected integration, or an If/Else or Wait that isn't filled in.

Cause 2: the trigger filters don't match

Symptom: some contacts enter and some don't, or the person you tested with never gets in. Confirm: Stats View, top left of the builder. Click the trigger and read Attempted, Matched and Unmatched. If your contact sits in Unmatched, click it, search them, and HighLevel shows why they didn't match.

HighLevel's rule is that a contact has to meet all the trigger's conditions and filters to enter. So a Form Submitted trigger filtered to Form A won't catch Form B, a Facebook lead trigger filtered to one form won't catch a duplicated form, and a Contact Tag trigger set to Added won't fire when the tag is removed. If you need either-or, add a second trigger. Separate triggers in one workflow each let contacts in on their own.

Also check the trigger fires at all for how the data came in. Tags don't trigger backwards: a tag added before the workflow was published won't enrol anyone. The Contact Changed trigger only sees new values, not removed ones. If leads from Facebook aren't reaching the CRM at all, that's an integration problem, and the full fix list is in Facebook lead ads.

Cause 3: re-entry is off (or they're still inside)

Symptom: it worked the first time and never again for the same person. Confirm: Settings tab inside the builder, Contact Settings, Allow Re-entry. Then open Enrollment History and search the contact to see if they're already in it or finished it.

Off means a contact can go through once, ever. On lets them back in after they finish or get removed, but never while they're still active, so someone sitting on a 7-day Wait can't start over. Appointment and invoice triggers are the exception: they let a contact in for every new appointment or invoice whatever the setting says.

Fix: turn re-entry on for things that should repeat (missed calls, review requests, reminders) and keep it off for one-time sequences. And test with a new contact. It's the first thing on HighLevel's own troubleshooting list, because an old test contact may already be blocked.

If the workflow runs on opportunities, check Allow multiple Opportunities on the same tab. Off means only the contact's first matching opportunity enters. It's on by default for new workflows and off for older ones, which catches people out on inherited accounts.

Cause 4: the contact is on DND

Symptom: the contact entered and the tags and pipeline moves happened, but the text or email never arrived. Confirm: open the contact and check the DND section at the bottom of the left column, then look at the SMS or email step in Execution Logs.

DND doesn't stop someone entering a workflow. It stops communication on the channels where it's on. And you might not have switched it on yourself: HighLevel turns on SMS DND when someone replies STOP or UNSUBSCRIBE, or when the carrier returns error 30003, 30004, 30005 or 30006, and turns on email DND after an unsubscribe, a spam complaint or a hard bounce. Conversations shows who enabled it: a workflow, a user or the contact.

Fix: only remove DND when the person really wants messages again. Permanent SMS DND needs the contact to text START, or proof of opt-in sent to support. If texts fail with no DND at all, it's usually the number or A2P registration, not the workflow. Start with A2P rejected? Fixes, and for missed-call texts specifically, the checks are in Missed call text back.

Cause 5: it's waiting, not broken

Symptom: the contact is in the workflow but nothing has gone out yet. Confirm: Highlight Contact Path from Enrollment History shows the step they're on.

Three settings hold messages on purpose. The Time Window (Settings tab) pauses texts, emails and calls outside the hours and days you set and sends at the next open slot. It doesn't hold tags or field updates, so those happen straight away and make it look half-run. A Wait step holds the contact until its time, date, reply or condition. And if you edit a Wait, anyone already sitting in it keeps the old timing. Only new arrivals get the change.

Contact timezone is the other one. If the workflow uses the contact's timezone and the contact has none, it falls back to the account's, so a 9 a.m. message can land at the account's 9 a.m., not theirs.

Cause 6: something removed them

Symptom: the contact started the workflow and dropped out partway. Confirm: Enrollment History status. Workflow Completed means they reached the end. Removed by Workflow Action means a step in this workflow did it (often a goal or Remove from Workflow). Removed by External Workflow Action means a different workflow pulled them out.

Stop on Response is the common one: a reply to any message this workflow sent ends it for that contact. That's usually what you want on a follow-up sequence. The other is a snapshot refresh: if a refresh deletes the step someone was waiting on, HighLevel removes them so they don't get stuck, and the log says "Removed by - Snapshot Refresh". Worth knowing before you push an update from GoHighLevel snapshots into live client accounts.

Cause 7: race conditions (and the 1-minute Wait fix)

HighLevel's definition: a race condition is two or more updates in the same second. They can run in the wrong order, or one can report it ran when it didn't. Their own example: the log shows Add Tag succeeded, but the contact has no tag, because an "Add to workflow" step and the Add Tag step fired in the exact same second.

Confirm: open Execution Logs and hover the dates to see the times. Two related steps with the same timestamp is your answer. The fastest way to the exact run is from the message itself: Conversations > open the message > message details > click the Workflow link, and it opens Execution Details with that contact and run already loaded.

Fix: put a Wait of 1 minute between the two steps. HighLevel says that with the 1-minute Wait "there is no chance of the race condition occurring." The pattern to look for is a step that adds a tag or updates a field, followed straight away by an If/Else that checks it, or by a step that pushes the contact into another workflow that reads it.

Missing Waits show up in AI-built workflows too. Reviewing one AI Builder made, I said "what this missed, is the wait step... right now they're going back-to-back" and that I'd "wait probably 24 hours or a day and then send the second SMS." As I put it, "sometimes it misses things." Read every AI-built workflow step by step before you publish it.

Cause 8: duplicate contacts

Duplicates cause both problems: a workflow that seems not to fire (it fired for the other copy of the contact) and people getting the same message twice. Confirm: Contacts > three-dot menu > Manage Duplicates (admins only), find by email or phone. Or trace the person's name in Workflow Maps (below) and see if two records show up.

Prevent it at Settings > Business Profile > Contact Deduplication Preferences. With Allow Duplicate Contact off, forms, Zapier, Facebook and Instagram update the existing contact matched on email (the default) or phone, with an optional second field. With it on, every submission can create a new record.

Merging with workflows running: per HighLevel's merge doc, the active run moves to the master contact. If the master is already in the same workflow, HighLevel keeps that run and ends the extra one, and Execution Logs shows a Contact Merge entry. Merges can't be undone, so pick the master carefully.

Same-trigger overlap looks identical: every workflow with the same tag trigger fires at once. Two old workflows both listening for "new lead" means two welcome texts.

Cause 9: an action failed (webhooks, integrations, premium steps)

Symptom: the contact entered, but a step errored and everything after it misbehaved. Confirm: Execution Logs highlights the Status or View Details of any failed action. Click Go To Action to jump straight to that step in the builder.

Get told about these instead of finding them weeks later. HighLevel's error notification setting (from its 2024 doc) emails sub-account admins when a workflow errors, at most one email every 24 hours, and lists them in a Needs Review tab on the Workflows page. It's off by default: turn it on in the account-wide workflow settings on the Workflows list page and add the people who should get it. The 2024 doc lists coverage for webhooks and custom webhooks, Slack, Array, Custom Code, ChatGPT, Google Sheets, Facebook custom audiences, Conversion API, Messenger and Instagram DM steps.

For WhatsApp flows with buttons: until Nov 10, 2026, a tap on a button or list option that used a custom value (like an appointment time) could drop the contact into the Timeout branch. HighLevel fixed that for every workflow automatically, and labels over WhatsApp's limit (20 characters on a button, 24 on a list option) are now shortened instead of failing to send. If you saw that before, test it again. Setup is in Set up WhatsApp.

Cause 10: the test lied to you

The classic Test Workflow button runs a workflow for a contact you pick, and HighLevel's own builder doc says it "isn't 100% perfect, especially if you reuse the same contact." So a test can pass while the live trigger never fires, because the test skips the trigger and the filters.

The new Test Workflow (a Labs feature: Agency Settings > Labs > The New Test Workflow) closes that gap. Open the trigger's Test tab, choose Test using events, turn on Listen for events (it listens for 15 minutes), then submit the real form. If the event shows up, the trigger works. Then test each action with that event's data. It runs for real, so tags get added and messages get sent: use your own contact.

Inherited an account? Use Workflow Maps

When a client hands you an account someone else built, the hard part is that nobody knows what fires what. Workflow Maps (Oct 27, 2026) draws it for you: Automation > Workflows > Workflow Maps (or Maps in the builder's top bar). Every workflow sits in its folder with the tags, forms, calendars and pipelines around it, so you can see the form that starts one workflow and the tag that starts the next. At launch it's for agency users and agency admins, and HighLevel's own doc says to check whether it needs Labs on your account.

Three tools in it I'd use straight away. Review workflows with errors lists every workflow with failed runs, split into Published and Draft. Pick one to see the failed step and the error, then Open in builder. Mark as read only clears the badge, it doesn't retry or fix anything. Contacts in the left rail searches by name, email or phone and shows every workflow that person went through in the last 60 days, and where they finished, are waiting or hit an error. Cleanup (Nov 10, 2026) lists workflows with default names, workflows with no enrollments in the last 60 days and empty folders. Check before you delete: a workflow with no recent enrollments might be a seasonal one.

The map's Assistant button answers "Explain what this workflow does" or "Help me investigate issues in this automation" about the account in front of you. It investigates, it doesn't fix: make the change in the builder yourself.

Workflow AI Analytics: ask what happened to a contact

Released Nov 9, 2026, this is the fastest way to answer "why didn't Sarah get the text?" Open the workflow, click the Workflow AI icon in the left bar and open the Chat tab. Ask for a named contact's path and you get their latest run step by step with the time and result of each step, plus a See contact path button that highlights it on the canvas. Repeat enrollments are called out so you know which run you're looking at.

It also answers the questions that used to take an hour on an inherited account. Ask it to follow one contact across all the workflows and it lists every workflow they entered, how many times and how each ended. "Who's in 3 or more workflows?" finds the contacts getting hit from every side, which is where double texts come from. "Compare the last 10 versions of this workflow" shows who changed what, and if you ask whether an edit broke it, the answer comes with a confidence level: Direct cause, Lines up or Can't tell. Ask for a PDF and you get a report you can send the client.

How I'd stop this happening on client accounts

Name every workflow and every action so the logs read like sentences. Keep one trigger per job, so two workflows never fight over the same tag. Put a 1-minute Wait after any step that changes data another step reads. Turn on error notifications for the people who'll act on them. And once a month, open Workflow Maps, review errors and run Cleanup.

Clients notice a broken automation as missing leads, and the money is made in the follow-ups, so a workflow that quietly stopped is the most expensive bug in the account. Checking it is part of what you charge a monthly fee for.

Start the 30-day trial and build workflows you can debug →
Start your 30-day free trial →

30 days free instead of HighLevel's usual 14, plus a 1:1 setup call with my team, weekly live calls and my agency resources from day one. See everything you get →

Other ways to start

My bonuses come with every one of these.

Best if you're new and want live help setting up

30-day trial + a free live setup bootcamp

Best if you're not sure which plan you need

Compare all 3 plans first

Best if you'll resell HighLevel as your own software

Go straight to the $497 Founder plan

FAQ

Why is my GoHighLevel workflow not triggering?

Usually it's still in Draft, the contact didn't match every trigger filter, or re-entry is off and they've been through before. Turn on Stats View in the builder to see if the trigger matched them, then read Execution Logs and Enrollment History.

How do I see why a contact didn't enter a workflow?

Open the workflow, turn on Stats View (top left), click the trigger and open Unmatched. Search the contact and HighLevel shows why they didn't match. Trigger stats cover the last 30 days.

Does DND stop a contact entering a workflow?

No. DND stops messages on the channels where it's on, so the contact can enter and get tags and pipeline moves while the SMS or email step doesn't send. Check the DND section on the contact.

What is a race condition in GoHighLevel workflows?

Two updates firing in the same second, so they run out of order or one reports success without applying. HighLevel's fix is a Wait of 1 minute between the two steps.

Why does my test work but the live workflow doesn't?

The classic Test Workflow enrols a contact directly and skips the trigger and its filters. Use the new Test Workflow (Labs) with Test using events and Listen for events to test the real trigger.

Where is Workflow Maps in GoHighLevel?

Automation > Workflows > Workflow Maps, or Maps in the builder's top bar. At launch (Oct 27, 2026) it's for agency users and agency admins, and HighLevel says to check whether Labs is needed on your account.

How do I get emailed when a workflow fails?

Turn on error notifications in the account-wide workflow settings on the Workflows list page and add the recipients. It's off by default and sends at most one email every 24 hours, with failures listed in the Needs Review tab.

Sources / last checked Nov 11, 2026

  • HighLevel help docs: workflow errors. Highlighting & Resolving Errors in a Workflow (modified Sep 15, 2026), Review workflows with errors (Oct 27, 2026), Troubleshooting Workflow Executions - Race Conditions (Feb 2, 2026) and Error Notifications in workflows (Sep 11, 2024), read Nov 11, 2026.
  • HighLevel help docs: workflow builder. Getting Started with Workflows (Aug 27, 2026), Workflow Builder Walkthrough (Sep 7, 2026), Workflow Settings Overview (Oct 14, 2026), Execution Logs & Enrollment History (Apr 15, 2026), Test Workflow (Nov 9, 2026), Contact Tag trigger (Jun 9, 2026) and Contact Changed trigger (Feb 4, 2026), read Nov 11, 2026.
  • HighLevel help docs: contacts. How to Use Do Not Disturb (Sep 28, 2026), Contact Deduplication Preferences (Apr 7, 2026) and How to Manage and Merge Duplicate Contacts (Sep 2, 2026), read Nov 11, 2026.
  • HighLevel help docs: Workflow Maps. Introduction to Workflow Maps (Oct 27, 2026), How to Use Workflow Maps (Oct 28, 2026), Trace a contact through workflows (Oct 27, 2026) and the AI Assistant in Workflow Maps (Oct 29, 2026), read Nov 11, 2026.
  • HighLevel changelog. Workflow Maps: Find and troubleshoot workflow errors (Oct 27, 2026), Test Your Workflow Right Inside AI Builder (Oct 29, 2026), Workflow AI Analytics (Nov 9, 2026), Workflow Maps: Clean up workflows and empty folders (Nov 10, 2026) and WhatsApp button and list replies now follow the right workflow branch (Nov 10, 2026), ideas.gohighlevel.com/changelog, read Nov 11, 2026.
  • My videos. My review of an AI-built reactivation workflow (Jul 2026) for the missing Wait step, quoted only and not embedded, and my Feb 2026 video for the follow-ups line. I don't have a dedicated troubleshooting video, so there's no video on this page.
Hamza Baig (Hamza Automates)

Author

Hamza Baig / Hamza Automates

Founder, Hexona Systems

I run Hexona Systems on GoHighLevel. HighLevel gave it the SaaSpreneur Platinum award in 2024 and Diamond in 2025 and 2026, and I spoke at their LevelUp event in 2026. Hexona powers 1,000+ agencies, we've served 1,500+ businesses, and I've taught 45,000+ students. Everything on this hub is something I use myself or have shown on camera.

Platinum SaaSpreneur
2024
Diamond SaaSpreneur
2025, 2026
LevelUp speaker
2026
YouTube subscribers, Oct 2026
34,200

Keep reading

Start your 30-day free trial →

30 days free + 1:1 setup call + my bonus / affiliate link