GoHighLevel Workflow Not Triggering? 12 Fixes

A lead fills out your form. You wait. No text, no email, no task. Your GoHighLevel workflow is not triggering, and you have no idea why.

We fix broken workflows every week, and the cause is almost never a bug. It is a setting, a filter or a step that does exactly what it was told. This guide gives you the 12 fixes we check, in order, plus a symptom table and a 15 minute test plan you can copy.

Quick answer: Most of the time the workflow is still in Draft, a trigger filter does not match, or the contact cannot re-enter because it is still active inside the workflow. Open the workflow logs first. If the contact never entered, fix the trigger. If it entered but nothing sent, look at waits, DND, time windows and Stop on Response.

First, Find Out Which Problem You Really Have

“Not triggering” can mean two very different things. Either the contact never entered the workflow, or it entered and then stalled. Do not touch the trigger until you know which one it is.

Open the workflow, go to the logs (Enrollment History and Execution Logs), and search for the contact. No record means the trigger or its filters blocked them. A record that stops on a step means the trigger worked and something later is holding the contact.

Use this table to jump straight to the right fix.

What you seeMost likely causeGo to fix
Nobody enters the workflow at allWorkflow is in Draft, or wrong trigger event1, 2
Some leads enter, others do notA trigger filter does not match their data3
Worked the first time, not the secondRe-entry is off, or the contact is still active inside4
First deal enters, second deal for the same contact does notAllow Multiple Opportunities is off5
Contact is in the workflow but nothing happens for daysStuck on a wait step with no timeout6
Texts go out hours late or next morningTime window or contact timezone7
Contact drops out halfwayStop on Response, a goal, or another workflow removed them8
Log shows the step ran but no SMS arrivedDND, bad phone number or A2P issue9
Log says tag was added but the contact has no tagRace condition10
Workflow ran fine, then suddenly stopped for one contactLoop lockout11
Trigger depends on Zapier, Make or FacebookThe outside tool never sent the event12

What GoHighLevel Users Keep Asking (Community, YouTube, Forums)

We read what people actually post about this. A few patterns keep coming up.

  • “Why can’t my contact go through the workflow again?” On the HighLevel ideas board, users ask for a way to queue contacts who try to re-enter a workflow they are still inside. Today that second entry is simply dropped.
  • “How do I pause one contact without starting over?” A request for a pause and resume button for a contact in an active workflow has been open since 2024 with dozens of votes. Right now you remove the contact and add them back, which starts from step one.
  • “My Zap stopped firing on stage changes.” In a long Zapier community thread, users reported the LeadConnector Pipeline Stage Changed trigger stopped starting their Zaps, and Zapier staff called it a known bug. The workaround people used was a webhook sent from a GoHighLevel workflow.
  • “The trigger works sometimes, not always.” Make users describe the same thing with LeadConnector watch events in the Make community, and again moved to webhooks.
  • “I did everything right and it still will not fire.” One YouTube walkthrough from StartupWise splits the causes into three groups in its chapters: missing or wrong triggers, filters that block contacts, and workflow settings like draft status and enrollment rules.

The 12 Fixes, in the Order We Check Them

1. Publish the Workflow (and Check Every Copy)

A Draft workflow ignores live events. This is still the number one cause we find. Watch for cloned workflows and snapshot imports, because they often arrive as drafts even when the original was live.

Fix: Switch the toggle to Publish and save. Then open your workflow list and look for any copy with the same name that is still in Draft.

2. Match the Trigger to the Real Event

“Contact Created” does not fire for a lead who already exists in your CRM. “Form Submitted” does not fire for a survey. “Appointment Status” is not the same as “Customer Booked Appointment”.

Fix: Write down the exact thing that happens in real life, word for word. Then pick the trigger with that exact name.

3. Strip the Trigger Filters, Then Add Them Back One by One

Every filter must match. One stale filter blocks everyone. Usual suspects: a cloned form (the page now uses “Form (Copy)”), a renamed stage, a replaced calendar, or a tag with different capital letters.

Fix: Screenshot the trigger. Remove all filters, test with a new contact, then add filters back one at a time. The one that stops enrollment is your culprit.

4. Understand How Re-entry Really Works

This one confuses almost everyone. Allow Re-entry off means a contact goes through once, ever. Allow Re-entry on still does not let a contact back in while it is still active in the workflow. HighLevel’s workflow settings guide says this plainly. So a lead who replies twice, or a test contact sitting on a 3 day wait, will not enter again.

Appointment and invoice triggers are the exception. They allow re-entry for each new appointment or invoice no matter what the setting says.

Fix: Turn on Allow Re-entry if you need it. If contacts must re-enter while still inside, split the workflow in two, or end the first run before the next event can happen.

5. Check Allow Multiple Opportunities

If you use opportunity triggers, this setting decides whether a second deal for the same contact starts its own run. When it is off, only the first opportunity enters. HighLevel turns it on for new workflows, but older workflows built before the feature came out have it off.

Fix: Open Settings in the workflow and turn it on if each deal should get its own follow up.

6. Find Contacts Stuck in Wait Steps

A wait for “contact reply” or “condition met” with no timeout can hold a contact forever. And here is the part most people miss: if you edit a wait step, contacts already waiting keep their old wait. Changing 7 days to 1 day only helps new contacts.

Fix: Add a timeout to every reply or condition wait. For contacts already stuck, remove them and add them back, knowing they start from the top.

7. Check the Time Window and Timezone

A time window pauses SMS, email and calls outside your hours, then sends at the next open slot. It does not pause internal steps like tags or field updates. So you see the tag added at 11 pm and think the SMS failed, when it is just waiting for 9 am. If the timezone is set to the contact’s timezone and the contact has none, the account timezone is used.

Fix: Check the window and timezone in Settings before you start rebuilding anything.

8. Look for Stop on Response, Goals and Remove Actions

Stop on Response pulls a contact out the moment they reply on any channel the workflow uses. A goal event or a “Remove from Workflow” step in another workflow does the same.

Fix: Check the contact’s log for the exit reason. Then search your other workflows for remove actions that point at this one.

9. Check DND, Phone Numbers and A2P

The workflow can fire perfectly and still send nothing. DND on that channel, a missing or invalid phone number, or a landline will all skip the SMS step. Carrier errors usually point to registration. Our guide on why A2P 10DLC gets rejected covers that side.

Fix: Open the execution log for the SMS or email step and read the reason it was skipped.

10. Watch for Race Conditions

When two actions hit the same contact in the same second, they can run out of order. HighLevel’s race condition article gives the classic example: the log says a tag was added, but the contact has no tag. That missing tag then fails to start the next workflow, and you blame the trigger.

Fix: Compare timestamps in the logs. If two steps fired in the same second, add a 1 minute wait before the second one.

11. Check for a Loop Lockout

If two workflows keep triggering each other, GoHighLevel steps in. A widely shared tutorial says a workflow that runs 50 times for one contact within 30 minutes gets locked, and an error shows at the top of the screen. After that, it stops running for that contact.

Fix: Look for pairs like “tag added starts workflow B, workflow B updates a field, field change starts workflow A, workflow A adds the tag again”. Break the loop with a filter or a check before the action.

12. Confirm the Outside Tool Sent the Event

If the lead comes from Facebook lead ads, Zapier, Make or a webhook, check that the contact even reached GoHighLevel. As the Zapier and Make threads above show, third party LeadConnector triggers have had long stretches of unreliable firing.

Fix: Check the contact’s created time against the lead time. Reconnect the Facebook page and form in Integrations. For Zapier or Make, read their task history, and consider sending a webhook from a GoHighLevel workflow instead of relying on their trigger.

Mistakes We See in Real Accounts

  • Testing with the owner’s own contact, which has DND on, old tags and five past enrollments.
  • Reply waits with no timeout, so contacts from last spring are still “in” the nurture.
  • Editing a wait step and expecting it to fix contacts already waiting.
  • A “Customer Replied” workflow that removes contacts from every other workflow, including the booking reminders.
  • Trusting Zapier for a core trigger with no backup, then losing a week of leads when it stops.

What Most Guides Skip

Most guides tell you to click the Resolve Errors panel and trust it. Do not. HighLevel’s own Resolve Errors article warns that pre-publish checks will not catch every problem. Errors that happen while the workflow runs only show in the Execution Logs. And a published workflow does not drop back to Draft when an error is found, so it can look “live” while every contact fails at step two.

The other thing nobody mentions: a broken workflow is often a working workflow that someone changed. A form swapped in a funnel, a stage renamed in a pipeline, a calendar replaced. Before you rebuild, ask what changed in the last week.

A 15 Minute Test Plan You Can Copy

Run this every time you build or fix a workflow.

  1. Create a brand new test contact with an email and mobile number you can check. Make sure DND is off.
  2. Confirm the workflow is Published and note the exact trigger and every filter.
  3. Trigger the event the way a real lead would. Use the live form on your phone, not the builder preview.
  4. Within 2 minutes, open the workflow logs. Is the contact enrolled? If not, go back to fixes 1 to 3.
  5. Read each step in the execution log. Note any step that was skipped and the reason given.
  6. Temporarily set long waits to 1 minute so you can see the full path, then set them back.
  7. Reply to the first message. Confirm Stop on Response and goals behave the way you want.
  8. Trigger the same event again with the same contact. Confirm the re-entry behavior is what you expect.
  9. Delete the test contact, restore the real wait times and write the trigger setup in the workflow description.

When to Get Help

If you have worked through this list and the workflow still fails, or you inherited a sub-account full of snapshot workflows nobody understands, a second pair of eyes saves time. Our GoHighLevel audit and fix service finds broken triggers, loops and stuck contacts, and you can start with a free GoHighLevel audit. If you are building from scratch, our GoHighLevel workflow automation playbook shows naming and testing habits that keep workflows easy to debug.

Frequently Asked Questions

Why is my GoHighLevel workflow not triggering?

The most common causes are a workflow left in Draft, a trigger that watches a slightly different event, a filter that does not match, or a contact that cannot re-enter. Check the workflow logs first to see if the contact entered at all.

Why won’t a contact re-enter my workflow even with Allow Re-entry on?

Allow Re-entry only works after a contact has finished or been removed. If the contact is still active inside the workflow, for example sitting on a wait step, the new trigger is ignored. Appointment and invoice triggers are the exception.

How do I get contacts out of a stuck wait step?

Remove them from the workflow and add them back, knowing they start from the first step. To stop it happening again, add a timeout to every reply or condition wait. Editing a wait step does not change contacts already waiting in it.

Why does my workflow work in test but not with real leads?

Test contacts usually have clean data and come through one path. Real leads may use a cloned form, a Facebook lead form or an integration, or be missing fields your filters need. Test with a fresh contact using the live path.

Why did my workflow trigger but no SMS was sent?

The contact may have DND on, no valid mobile number, or your number may not be on an approved A2P 10DLC campaign. A time window can also hold the text until the next open slot. The execution log shows the reason.

Why does the log say a tag was added but the contact has no tag?

That is usually a race condition, where two actions run in the same second. HighLevel recommends adding a 1 minute wait before the action that conflicts.

Why did my Zapier or Make trigger for GoHighLevel stop firing?

Users in the Zapier and Make communities have reported LeadConnector triggers that stopped or fired unreliably. Check the task history, and consider sending a webhook from a GoHighLevel workflow instead.

Want this done for you?

Our certified GoHighLevel experts can set it up for you, usually in 2 to 4 weeks with 30 days of free support. See our GoHighLevel workflow automation services.

Book a Free Consultation

Similar Posts

5 Comments

Leave a Reply

Your email address will not be published. Required fields are marked *