GoHighLevel Workflow Re-Entry Settings Explained (2026)

By Dr Priya Jaganathan, GoHighLevel Certified Admin · HL Growth Partner, Australia · Updated 2 October 2026 · 10 min read

GoHighLevel workflow re-entry is one of those settings most people never look at until a client rings to ask why a lead got the same welcome email three times. It sits quietly in the workflow Settings tab, and a single toggle decides whether a contact can go through an automation once or many times.

In this guide I'll explain exactly what the HighLevel Allow Re-entry setting does, what happens when a trigger fires while a contact is still mid-workflow, when to switch it on or off, and how to test your setup before it touches a real customer.

What the GoHighLevel workflow re-entry setting actually does

Every workflow in HighLevel has a Settings tab alongside the builder. Inside it you'll find the Allow Re-entry toggle, which controls whether the same contact can be enrolled in that workflow more than once over its lifetime.

With the toggle ON, a contact who has finished the workflow, or who was removed from it, can be enrolled again the next time the trigger fires. With the toggle OFF, the contact gets one pass and every later trigger event is ignored for that workflow.

How to find the setting

• Go to Automation in the sub-account sidebar and open Workflows.
• Open the workflow you want to check (or create a new one).
• Click the Settings tab at the top of the builder.
• Find Allow Re-entry and set it ON (blue) or OFF (grey), then save.

HighLevel's own Workflow Settings overview covers the rest of the tab, which is worth reading if you inherited an account.

The default changed, so check older workflows

HighLevel announced in its changelog that Allow Re-entry is now ON by default for newly created workflows. Previously it defaulted to OFF.

That means an account can contain a mix of older workflows set to OFF and newer ones set to ON, without anyone having made a conscious decision. Audit the setting on every live workflow rather than assuming they all behave the same way.

What happens when the trigger fires while a contact is still active

This is the part that catches most people out. Allow Re-entry only applies once a contact has left the workflow, either by completing it or by being removed.

If a contact is still active, for example sitting on a three-day wait step, and the trigger fires again, they are not enrolled a second time. The new trigger event is skipped for that contact, even with re-entry ON.

In practice, that means:

• A lead who submits your enquiry form twice in an hour will not get two parallel nurture sequences.
• A lead who submits it again a month later, after the sequence finished, will start again if re-entry is ON.
• If you need the new event to restart the journey immediately, you must remove the contact first and then let them re-enter.

The appointment and invoice exception

Workflows that use an appointment or invoice-based trigger behave differently. HighLevel allows a contact to enter these multiple times, once per appointment or invoice, regardless of the re-entry setting.

If you're building reminder sequences, my guide to appointment reminder workflows that cut no-shows walks through the full setup.

When to turn HighLevel allow re-entry on vs off

The right answer depends on whether the journey is meant to happen once in a customer's life or every time a certain event happens. I use a simple test: "Would I be embarrassed if this contact got this sequence twice?" If yes, switch it off.

Re-entry ON: the recurring journeys

Recurring workflows are built around events, not people. A dental clinic's six-monthly check-up reminder, a gym's membership renewal, or a trades business's annual service notice all need to run every cycle for the same contact.

For these, re-entry ON is essential. Just make sure the workflow actually ends (or removes the contact) before the next cycle starts, otherwise the "already active" rule will block the next run.

Re-entry OFF: the once-in-a-lifetime journeys

Welcome sequences, onboarding and first-time lead magnet delivery are about a relationship starting. Running them twice confuses the customer and can double up tasks for your team.

How workflow re-entry interacts with goals and removal actions

Re-entry rarely works alone. Three other tools shape when a contact leaves a workflow, and therefore when they become eligible to re-enter.

Goal Event action

The Goal Event action lets a contact jump straight to a defined point in the workflow when they hit a milestone, such as clicking a trigger link, submitting a form or making a payment. If the contact reaches the goal step without meeting it, you choose to end the workflow, continue anyway, or wait until the goal is met.

When a goal ends the workflow, the contact completes it, so with re-entry ON they can be enrolled again on the next trigger. I cover the patterns in detail in setting up workflow goals and exit conditions.

Remove from Workflow action

The Remove from Workflow action takes a contact out of the current workflow or another workflow you choose. It's the cleanest way to stop a sequence when something changes, such as a lead booking a call mid-nurture.

Because a removed contact counts as having left, removal plus re-entry ON means they can be enrolled again the next time the trigger fires. That's useful for restarts, and dangerous if the trigger fires again by accident.

Add to Workflow action

The Add to Workflow action enrols a contact into another workflow from inside the current one. The destination workflow's own re-entry setting still applies, so if that workflow has re-entry OFF and the contact has already been through it, nothing happens.

Tag-trigger loops: how re-entry causes duplicate sends

The most expensive re-entry mistake I see is a tag loop. Workflow A adds a tag, Workflow B triggers on that tag and later removes and re-adds it, or adds a tag that triggers Workflow A again.

With re-entry ON on both workflows, each completion makes the contact eligible to start again. The result is duplicate SMS, repeated emails and, in the worst cases, a contact being messaged every few minutes until someone notices.

To prevent tag-trigger loops:

• Never let a workflow add the same tag that triggers it.
• Add trigger filters so a tag only fires for contacts who don't already hold a "processed" tag.
• Map which workflows add which tags before you publish anything new.
• Use re-entry OFF on any workflow whose trigger is a tag that other automations touch.

For a deeper checklist, see my guide to contact tag trigger safeguards. And if you're unsure how a particular trigger behaves on repeat events, the complete workflow triggers reference lists what each one listens for.

How to test GoHighLevel workflow re-entry before going live

Never trust a re-entry setting you haven't tested. I use a dedicated test contact with my own email and mobile so I see exactly what a customer would receive.

1. Create a test contact. Use an email and phone number you control, and tag it clearly (for example "internal-test").
2. Run the first enrolment. Use the Test Workflow option in the builder, or fire the real trigger (submit the form, add the tag) to mimic real behaviour.
3. Fire the trigger again while active. Confirm the contact is not enrolled a second time while still mid-workflow.
4. Let it complete, then fire again. With re-entry ON, the contact should start over. With re-entry OFF, nothing should happen.
5. Check the logs. Open the workflow's Execution Logs and Enrollment History to see each enrolment, step and any skipped or errored actions.

Keep in mind that testing from the builder can bypass the trigger itself, so it won't always show you how re-entry behaves on a real trigger event. Firing the actual trigger on your test contact is the more honest test. My workflow testing and debugging guide covers the full process.

Reading the logs

Execution Logs show a contact's journey through each action, wait and decision, with details on any error. Enrollment History shows when a contact entered the workflow and how.

If you see two enrolments close together for the same contact, you have a re-entry or trigger problem. If you see none on the second event, either re-entry is OFF or the contact was still active.

Common mistakes to avoid

• Assuming every workflow uses the same default, when older workflows may still have re-entry OFF.
• Leaving re-entry ON for welcome or onboarding sequences, then wondering why clients get duplicate welcome emails.
• Expecting re-entry to restart a workflow for a contact who is still active in it.
• Building tag loops where one workflow's tag triggers another that re-triggers the first.
• Using Add to Workflow without checking the destination workflow's own re-entry setting.
• Testing only with the builder test option and never firing the real trigger on a test contact.

If you want a second pair of eyes on your workflow re-entry settings, tag logic and duplicate-send risks across your sub-accounts, book a strategy call with the HL Growth Partner team.

Book Your Strategy Call →

Frequently asked questions

What does Allow Re-entry do in a GoHighLevel workflow?

Allow Re-entry controls whether a contact can enter the same workflow more than once. When it is ON, a contact can be enrolled again after completing the workflow or being removed from it. When it is OFF, a contact can only go through the workflow one time.

Can a contact re-enter a workflow while they are still active in it?

No. Even with Allow Re-entry ON, a contact who is still active in the workflow will not be enrolled again when the trigger fires. They must complete the workflow or be removed before they become eligible to re-enter.

Is Allow Re-entry on or off by default?

HighLevel changed the default so that Allow Re-entry is ON for newly created workflows. Older workflows may still be set to OFF, so it is worth checking the Settings tab on every live workflow in the account.

Do appointment reminder workflows need re-entry turned on?

Workflows with appointment or invoice-based triggers allow a contact to enter once per appointment or invoice regardless of the toggle. Many builders still switch re-entry ON for clarity, but the trigger type is what guarantees each booking gets its own reminders.

Should a welcome sequence allow re-entry?

Generally no. A welcome or onboarding sequence is meant to run once, and replaying it for a returning contact looks careless. If returning leads need follow-up, send them to a separate workflow designed for that situation.

Why is my contact receiving the same message multiple times?

The most common cause is a tag-trigger loop combined with re-entry ON, where workflows keep adding tags that re-trigger each other. Check the Enrollment History for repeat enrolments, map which workflows add which tags, and switch re-entry OFF where a sequence should only run once.

How do I test whether re-entry is working correctly?

Use a test contact with your own email and mobile, fire the real trigger once, then fire it again both while the contact is active and after they finish. Review the Execution Logs and Enrollment History to confirm each enrolment happened, or was skipped, exactly as you expected.

Related Articles on HL Growth Partner

Fixing workflow problems

• Troubleshoot and fix common GoHighLevel workflow errors
• Stop silent automation failures with error handling
• Merge and prevent duplicate contacts in HighLevel

Building smarter workflows

• If/Else conditions guide for HighLevel workflows
• Wait steps and business hours explained

Keeping workflows organised

• Workflow folders and naming conventions
• Use version history to roll back workflow changes