Automation Wait Steps Not Working: Timing, Time Zone and Scheduling Problems
When automation wait steps are not working, contacts resume too early, too late or never. The cause is in the wait duration, the wait condition, the time zone or the scheduling logic. Do not assume all platforms calculate waits identically, because time zone handling varies and that alone changes when a contact resumes.
Table of Contents
- 01.Where wait steps fail
- 02.What to check first
- 03.Time zones and business hours
- 04.Wait until conditions
- 05.Wait duration and entry time
- 06.Resume conditions and scheduling
- 07.How to test it
Where wait steps fail
A wait step pauses a contact for a duration or until a condition is met. When it fails, the contact resumes at the wrong time or not at all. The failure is usually in the wait configuration, the time zone or the resume condition. A wait that uses the wrong time zone resumes at a different wall-clock time than expected. A wait until a condition that never becomes true stalls forever. A wait during business hours can skip or stall depending on how business hours are defined.
| Failure | Symptom | Common cause |
|---|---|---|
| Wrong time zone | Resumes at unexpected hour | Account vs contact time zone |
| Condition never met | Contact stuck in wait | Field never updated |
| Business hours gap | Stalls overnight or weekend | Business hours not configured |
| Resumes too early | Wait shorter than expected | Duration unit wrong |
| Daylight saving shift | Off by an hour | Time zone without DST handling |
What to check first
- Confirm the wait duration and the unit, such as hours, days or minutes.
- Check which time zone the wait uses, account or contact.
- If the wait is until a condition, confirm that condition can actually be met.
- Check business hours configuration if the wait respects them.
- Compare the expected resume time to the actual resume time for a test contact.
Time zones and business hours
Time zone is the most common wait step problem. A wait of one day means one day in a specific time zone. If the account time zone is different from the contact time zone, the contact resumes at a different local time than you expect. Some platforms let you use the contact time zone, others use the account time zone. Confirm which one applies. Business hours add another layer. A wait until the next business hour stalls if the contact enters outside business hours and the configuration does not handle it. Daylight saving can shift a wait by an hour if the time zone does not account for it.
Wait until conditions
A wait until a condition resumes the contact when the condition becomes true. If the condition depends on a field that is never updated, the contact stays in the wait indefinitely. Confirm the field the condition checks will actually change. A wait until a status changes will not resume if the status is never updated by another workflow or a manual action. Check whether the condition can realistically be met within the workflow timeline.
Wait duration and entry time
The wait duration starts when the contact reaches the wait step, not when the workflow started. A contact that enters the workflow late reaches the wait step late and resumes late. Confirm the entry time and the wait start time. A duration set in the wrong unit, such as hours instead of days, produces a much shorter wait. Check the unit and the duration value together.
Resume conditions and scheduling
Some waits resume only on certain days or during certain hours. A wait configured to resume only on weekdays will hold a contact over the weekend. A wait that resumes only during business hours will hold a contact until the next business hour. Confirm the scheduling rules on the wait step. These rules are useful but they change the resume time, so they need to match your intent. Sending messages at the wrong time because of a wait configuration is covered in the guide on automation sending messages at the wrong time.
How to test it
- 1.Enroll a test contact and note the exact time it reaches the wait step.
- 2.Record the expected resume time in the relevant time zone.
- 3.Check whether the contact resumes at the expected time.
- 4.If it does not, check the time zone, duration unit and scheduling rules.
- 5.If the wait is until a condition, confirm the condition is met during the test.
Frequently Asked Questions
Why is my automation wait step resuming at the wrong time?
The wait may use a different time zone than you expect, the duration unit may be wrong or business hours scheduling may be shifting the resume time. Check the time zone, the duration unit and any scheduling rules on the wait step.
Why is my automation stuck in a wait step?
If the wait is until a condition, the condition may never be met because the field it checks is never updated. Confirm the condition can realistically become true within the workflow timeline.
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
Automation Is Sending Messages at the Wrong Time: What to Check
A message at the wrong time is either a scheduling problem or a delivery delay. Check the send timestamp in the platform first to distinguish the two.
Automation Conditions Not Working: How to Troubleshoot If/Else Logic
When contacts take the wrong branch, the condition evaluated against unexpected data. Check the actual field values before changing the condition rules.
Automation Workflow Stops Halfway: How to Find Where It Breaks
A workflow that stalls ran successfully up to a point then failed or waited. Trace the workflow step by step through the history instead of rebuilding everything.