HighLevel Workflow Wait Step Not Releasing Contacts? How to Troubleshoot It

Where exactly is the contact waiting?

Don’t start by changing the workflow. Find the contact first.

• In the workflow: open it, then Execution Logs. Steps with errors are highlighted, and Enrollment History shows how each contact moved through it (Execution Logs).
• From a message: in Conversations, open the message details and click the workflow link. HighLevel opens the execution with the contact already selected.
• Across workflows: go to Automation, Workflows, Workflow Maps, open Contacts and search by name, email or phone. HighLevel shows each workflow the contact went through and whether it finished, is waiting, or hit an error, for the last 60 days (Trace a contact).

Once you know the step, note the time the contact entered it. You will need it below.

What kind of Wait step is it?

The Wait action has many types, and they release contacts very differently (Wait Action):

• A set period of time releases after the duration.
• A specific date and time, fixed or read from a contact field.
• A recurring schedule, released at the next matching occurrence.
• An upcoming appointment or booking, before, at or after the appointment, service booking or invoice due date.
• The contact to reply, the contact to take an action and a user to reply, each with an optional timeout.
• Specific conditions to be met, released when any one segment of conditions becomes true, with an optional timeout.

The reply, action and condition types are where most “stuck” contacts are. Without a timeout, they wait until the thing happens. If the contact never replies or the tag is never added, they wait. Turn the timeout on and decide what happens when it runs out.

For condition waits, HighLevel says each segment is checked on its own and the contact moves on as soon as any one is true. If you meant “all of these”, put the conditions in one segment joined with AND, not in separate segments.

Is a time window or timezone holding them?

Two settings can make a correct wait look broken:

• Advance Window on a time-based wait lets you resume only on chosen days or between chosen hours (Wait Action). A one-hour wait that ends on a Saturday with a Monday to Friday window resumes when the window next opens, on Monday.
• The workflow’s Time Window pauses communication actions like emails, SMS and calls outside the hours you set, and resumes them at the next allowed slot. Internal actions such as adding a tag are not affected (Workflow Settings). So the wait may have ended on time, while the text after it is held until morning.

Check the timezone too. Workflow settings let you run time-based actions on the account timezone or each contact’s timezone, and contacts with no timezone fall back to the account’s (Workflow Settings). A wait set for 9 AM can release at a time that looks wrong to you but is right for the contact.

Is the date already in the past, or missing?

For date and appointment waits, the step has an If this date has already passed option: continue, exit the contact, go to a specific step, or skip outbound communication until the next wait (Wait Action). If contacts are skipping ahead or leaving the workflow, that option is usually why.

For dynamic dates, the value is read from the contact’s field when the contact reaches the step. Open a few stuck contacts and check that the field actually has a date in it.

I changed the Wait step. Why didn’t anything happen?

HighLevel says contacts already in a Wait step keep the wait they had when they entered. Editing the step only affects contacts who arrive after the change, while edits to later steps can apply when the waiting contacts move on (Wait Action FAQ).

So fixing the step does not release the contacts who are already stuck. You need to move them on yourself. Be careful re-adding them: with Allow Re-entry on, HighLevel says a contact can only enter again after finishing or being removed, never while still active (Workflow Settings).

What if many contacts are stuck past their time?

If the wait is a plain time delay, there is no window or timezone that explains it, and a batch of contacts is still waiting well past their release time, it may not be your configuration. Check the HighLevel status page first.

Then open a support ticket with what they need to investigate: the workflow name, the Wait step, three or four affected contacts, when each should have been released, and screenshots from Execution Logs. While you wait, decide whether those contacts need a manual nudge so nobody misses an appointment reminder.