GoHighLevel Workflow Wait Steps Not Working as Expected
When a GoHighLevel workflow seems stuck at a wait step, it may actually be working as configured. Wait steps depend on duration, time zone and business hours, and a small setting can make a contact wait far longer than you expect. This guide covers how to diagnose wait steps that behave unexpectedly.
Table of Contents
- 01.When a wait is not really broken
- 02.What to check first
- 03.Duration versus specific time
- 04.Time zone mismatches
- 05.Business hours restrictions
- 06.Event-based waits
- 07.How to diagnose a wait step
When a wait is not really broken
A contact sitting at a wait step is usually waiting as configured, not stuck. The wait may be set to a specific time of day, a certain day of the week or within business hours only. Before assuming the workflow is broken, read the wait configuration and confirm it matches what you intended.
What to check first
- Open the workflow history and find the wait step.
- Read the wait type, duration and target time.
- Check the time zone the wait is calculated in.
- Confirm whether business hours restrict the wait.
- Note when the wait is scheduled to end.
Duration versus specific time
A wait can be a fixed duration or a specific time of day. A fixed duration waits a set amount from the previous step. A specific time waits until a clock time, which can mean a much longer wait if the contact reaches the step just after that time. Confirm which type the step uses and whether the long wait is just the gap until the next occurrence.
Time zone mismatches
A wait set to a specific time is calculated in a time zone. If the wait uses the account time zone and the contact is in another, the wait ends at a different local time than expected. Confirm which time zone the wait uses and compare it to the contact's time zone if the timing looks wrong.
Business hours restrictions
A wait restricted to business hours will hold a contact until the next business hours window. A contact who reaches the step on a Friday evening may wait until Monday morning. If the wait seems too long, check whether business hours are restricting it and whether the configured hours match your actual schedule.
Event-based waits
Some waits depend on an event, like an appointment time. A wait set to send a reminder before an appointment depends on the appointment being booked. If the contact has no appointment, the wait has nothing to calculate from and may hold indefinitely. Confirm the contact has the data the event-based wait depends on.
How to diagnose a wait step
- 1.Find the wait step in the workflow history.
- 2.Read the wait type, duration and target time.
- 3.Check the time zone and business hours settings.
- 4.Calculate when the wait should end based on those settings.
- 5.Confirm the contact has any data an event-based wait needs.
Frequently Asked Questions
Why is my GoHighLevel workflow wait step not working?
The wait may be set to a specific time, restricted to business hours, calculated in the wrong time zone, or dependent on an event the contact does not have. Read the wait configuration in the workflow history and confirm the type, time zone and business hours match what you intended.
Why does my GoHighLevel wait step take so long?
A wait set to a specific time of day can hold a contact until the next occurrence, and a wait restricted to business hours can hold a contact over a weekend. Check the wait type, time zone and business hours to see whether the long wait is just the configured gap.
Need help applying this to your business?
PPC, Conversion Tracking, CRM and Automation Specialist. Helping businesses generate qualified leads with Google Ads, accurate tracking and automated follow-up.
Related Guides
GoHighLevel Workflow Stops Halfway: How to Find the Problem
A workflow that starts but stops before finishing leaves a clear trail in the history. This guide covers wait steps, condition exits, failed actions and missing data for later steps.
GoHighLevel Workflow Conditions Not Working: A Troubleshooting Guide
When if/else branches send contacts the wrong way, the conditions are usually the cause. This guide covers wrong operators, empty fields, AND or OR logic and data type mismatches.
gohighlevel-workflow-history-troubleshooting
Workflow history is the fastest way to find why a contact did or did not go through a workflow. It shows every step, every wait and every exit reason. This guide covers how to read workflow history to find the exact point a workflow stops.