If you set up an automation in GoHighLevel and nothing is happening — the lead never gets the message, the tag doesn't apply, the pipeline stage doesn't move — you're not alone. It's one of the most common complaints I see in accounts I review: the business trusted the system to run on its own, and at some point it quietly stopped working until a client complained about never hearing back.
The good news is it's almost never a platform problem. GoHighLevel doesn't just "break" for no reason — there's a specific cause, and it almost always lives in one of five places. Let's go through them one by one, with a checklist you can run yourself before assuming you need to rebuild everything from scratch.
The symptoms that tell you something is broken
Before diagnosing, here are the typical warning signs:
- A new lead enters the CRM but never gets the welcome message.
- A contact gets "stuck" on a pipeline stage even though it met the condition to move forward.
- Tags don't apply automatically when they should.
- A follow-up sequence stops halfway through — the first message goes out, the second never arrives.
- A contact who already went through the flow before doesn't re-enter when they should (a reactivated client, for example).
Any of these points to something breaking in the chain of trigger → condition → action at one specific spot, not to "GoHighLevel just stopped working" in general.
The five real causes behind a broken automation
1. The trigger is misconfigured
The trigger is the event that tells the workflow "start now." If the trigger is listening for the wrong event — say, "form submitted" when the lead actually comes in through an inbound call, or "tag added" when the tag is actually applied manually instead of automatically — the workflow never starts because the event it's waiting for never happens exactly as defined.
This happens a lot to businesses migrating from another system or copying a generic template workflow without adjusting the trigger to how leads actually reach their specific business.
2. An if/else condition that never matches
Inside the workflow, condition steps filter who goes down which branch. The problem shows up when the filter is set wrong: it compares a custom field against a value with different capitalization, checks for a tag that's actually named slightly differently, or requires a numeric field to be "greater than" when it should be "greater than or equal to." The contact enters the workflow, hits the condition, doesn't match it as written, and just sits there — no visible error, no progress.
3. The workflow got paused without anyone noticing
By far the most common one. Someone paused the workflow to test something, to edit a step, or just to review it — and forgot to turn it back on. GoHighLevel doesn't send any alert like "this workflow has been paused for two weeks," so a lot of time can pass before anyone notices leads stopped getting followed up with.
4. Re-entry is turned off
Every trigger has a re-entry setting (whether a contact can enter the workflow again after already going through it once). If it's off and you have a contact who needs to go through the same flow again — a client who returns months later, a reactivated lead — they simply can't get back in, even if they trigger the event again.
5. An earlier step fails silently
If an early step in the workflow depends on data that doesn't exist (an empty custom field, a phone number in the wrong format, an external integration that didn't respond), that step can fail without the rest of the workflow ever knowing — and everything downstream just never runs for that contact.
Quick diagnostic checklist
Before rebuilding anything, run through this in order:
- Check the workflow's Published/Draft switch. If it says Draft, that's your answer.
- Open Execution Logs and find a specific contact who should have gone through the flow. The log tells you exactly which step it stopped at.
- Check the trigger's configuration — is the event it's waiting for exactly what happens in your real process?
- Check every condition step — compare the exact values (capitalization, spacing, exact tag or stage name) against what the contact actually has.
- Verify re-entry if the contact already went through the workflow before.
- Test with a real test contact — don't assume, run one through yourself and follow the flow step by step.
A typical case
In accounts I review regularly, I see the same pattern: a lead follow-up workflow that worked fine for the first few months, and at some point someone edited it — added a step, changed a condition, tested something — and never re-tested the full flow end to end after the change. The workflow still shows as "published" and looks active, but one specific branch stopped working for a particular type of lead. Nobody notices until they check how many leads of that type never got followed up with, weeks later.
This ties directly into one of the most common GoHighLevel configuration mistakes: not testing the whole system after every change, not just the first time you build it.
How to keep it from happening again
- Test every change with a test contact before calling it done, not just the first time you build it.
- Document what each workflow does in a simple note — what trigger it uses, what conditions it has, which other workflow it hands the contact to. Without this, every person who edits something is working blind.
- Check Execution Logs periodically, not just when someone complains. Ten minutes once a month can catch a paused workflow before it costs you real leads.
- Avoid two workflows competing for the same trigger or the same pipeline stage without being coordinated with each other.
When to bring in an expert
If you've gone through the checklist and still can't find where it's breaking, or your account has so many workflows edited over time that nobody really knows how they connect anymore, that's the point where an outside audit is worth more than continuing to guess. It's exactly the kind of review I do as part of GoHighLevel CRM setup: go into the account, map every automation, and leave it documented — and working.
Stop losing leads to a broken automation
Every day a broken workflow keeps "running" without actually doing anything is a lead that never got followed up with, or a client left waiting for a message that never came. Book 15 minutes and I'll review with you which specific automation isn't working — or, if you'd rather have a full account audit with a written diagnosis, the $99, 2-hour consultation covers exactly that.