Home/HighLevel/Troubleshooting/Workflow not triggering

Troubleshooting · Workflows

Fix: GoHighLevel workflow not triggering. Published, filtered, tested.

When a workflow does not start, the cause is usually simple: it is still in draft, the trigger filter does not match the event, or the event never happened the way you think.

  • 5likely causes
  • 6fix steps
  • 1escalation path
SymptomCausesFixConfirm
5
Likely causes5 to check1 ruled out
Diagnosis
Workflows · SymptomWorkflow not triggering
Issue
1Workflow in draftRuled out
2Filter mismatchChecking
3Wrong triggerTo check
4Re entry blockedTo check
5Event did not happenTo check
6 fix stepsPublished, filtered, tested.Fix it, then confirm it works

The short answer

A GoHighLevel workflow usually fails to trigger because it is still in draft or not saved, the trigger filter does not match (for example the wrong form), the wrong trigger type was chosen, or re entry settings block a contact who already went through.

Michael is a sponsored HighLevel affiliate. Links to HighLevel use his partner link at no extra cost to you. HighLevel prices and product facts on this page come from HighLevel's own pricing page and help center, checked on the date above.

Causes

Why is a HighLevel workflow not triggering?

Most cases come down to the five causes in this table. Check each one before you change anything.

CauseHow to check
Workflow in draftStatus shows Draft
Filter mismatchTrigger filter names the right form, calendar or tag
Wrong triggerTrigger matches the real event
Re entry blockedWorkflow settings for re entry
Event did not happenContact activity timeline

Diagnose

How do you confirm why the workflow did not trigger before you rebuild it?

Use one real example. Pick a contact who should have started the workflow and open two things side by side: the contact's activity timeline and the workflow history in Automation. The timeline tells you whether the event happened. The history tells you whether the workflow saw it.

That gives you three cases. The event is not on the timeline: the workflow is innocent, and the form, calendar or integration upstream is where to look, such as forms not submitting. The event is there and the contact is in the history: the workflow did trigger, and what you are missing is a later step. The event is there and the contact is not in the history: now it is a trigger problem.

For a real trigger problem, read the workflow in this order. Is the status Published, not Draft, and was it saved? Does the trigger match the real event? Does each filter name the exact form, calendar or tag? Without a filter, every form submission starts the workflow, and a filter on the wrong form starts none of the ones you want. Then check re entry in the workflow settings, since old test contacts are often blocked there. If only some contacts are missed, see contacts not entering a workflow.

Fix

Fix it step by step.

  1. Confirm the workflow is published and saved.
  2. Open the trigger and check every filter.
  3. Check the contact timeline to confirm the event happened.
  4. Check workflow settings for re entry rules.
  5. Test with a brand new contact.
  6. Check the workflow history for errors.

Still stuck

When to contact support.

If none of these fix it, open Help and Support from the question mark at the top right of your agency view, then start a chat (AI Support Chat or Agent Chat), join a Zoom call or open a ticket. Have your Agency Relationship Number and the Location ID of the subaccount ready, add screenshots of the problem, and turn on Support Access so the team can look inside the account. Only Agency Admins and Agency Users can reach HighLevel support; subaccount users go through their agency.

  • Name triggers clearly
  • Test every workflow with a fresh contact before launch

If it is published, the filters match and a fresh contact still does not enter, send support the workflow name, the contact, the time of the event and screenshots of the trigger and the contact timeline.

For prevention, name triggers clearly, keep one job per workflow and test with a brand new contact before launch. See build your first workflow and the workflow glossary entry. If contacts enter and then stall, see workflow stuck on a wait step.

For more on building them, see the workflow answers and the GoHighLevel workflows guide. Still evaluating? Start with the 30 day GoHighLevel free trial through Michael's link and test this in your own account. For an honest look at strengths and limits, read the HighLevel review.

Help & Support
Opens from the question mark at the top right of the agency view
Relationship Number0 000 000
1
Support AccessLets support look inside your account for a set time
3
Quick support actions
Start Chat
5
Before you contact supportHave these ready
1
Agency Relationship NumberTop of Help and Support, with a copy button
2
Location ID of the subaccountSettings, Business Profile, or the URL after /location/
3
Support Access turned onAgency Settings, Company, Advanced Settings. It expires on the date you pick
4
Screenshots and the exact errorWhat you did, what you expected, what happened
5
Pick a channelAI Support Chat, Agent Chat, a Zoom call, or a ticket by email
Agency Admins and Agency Users onlyBilling or login: +1 (888) 732 4197
Michael Reimer, Founder of CRM Pros
Michael's takeFounder of CRM Pros · HighLevel Commander

Test with a fresh contact. Old test contacts often hit re entry rules.

Questions

Common questions.

Why is my GoHighLevel workflow not triggering?

A HighLevel workflow usually fails to trigger because it is still in draft or not saved, the trigger filter does not match (for example the wrong form), the wrong trigger type was chosen, or re entry settings block a contact who already went through.

How do I prevent it?

Name triggers clearly, keep one job per workflow and test with a brand new contact before launch.

When should I contact HighLevel support?

Contact support once you have checked every cause on this page and it still fails, or when the fix sits on HighLevel's side. If it is published, the filters match and a fresh contact still does not enter, send support the workflow name, the contact, the time of the event and screenshots of the trigger and the contact timeline.

Does a draft workflow run?

No. A draft workflow does nothing. Publish it, then save.

Why does my workflow start for the wrong form?

The trigger has no filter, or the filter names a different form. Without a filter, every form submission starts the workflow. Add a filter for the exact form.

How do I test a workflow trigger?

Publish and save the workflow, then fire the event with a brand new contact, such as submitting the form yourself. Open the workflow history and confirm the contact entered.

Next step

See it in your own account. Thirty days, every feature.

Start a 30 day trial through Michael's link, build the first system and test it before the first invoice. Usage fees for phone, SMS, email and AI can apply during the trial.

HighLevel has three plans at a flat monthly price, each with unlimited users and contacts. See what each one includes and what it costs.

Compare the PlansStarter, Unlimited and Founder
⌃

Site preview

Explore the next page

This destination is reserved in the page inventory and is not built yet.