The Wait step
The step that pauses a flow for a set time: the amount and unit settings, its relationship with the 24-hour window, its role in breaking loops, and how it resets the consecutive-send counter.
Last updated: September 30, 2026
Loading…
The step that pauses a flow for a set time: the amount and unit settings, its relationship with the 24-hour window, its role in breaking loops, and how it resets the consecutive-send counter.
Last updated: September 30, 2026
Sending an offer straight after a greeting drives people away; sending it half an hour later creates a second chance. The Wait step pauses the flow for as long as you say and then carries on from where it left off. This guide covers the step's two settings, its relationship with Meta's 24-hour rule, and its two important side effects inside a flow.
The step sends nothing and changes nothing. It only waits. When the time is up, the flow continues from Next.
It does not wait for the person to write — that is a different thing (the "Wait for a typed reply" setting in The Message step, or The Collect information step). The Wait step only watches the clock.
Typical uses:
The step works on both channels.
How much to wait: a number between 1 and 100,000.
Three options: minutes, hours, days.
Together they give the waiting time: 30 minutes, 2 hours, 3 days.
The total wait cannot exceed the platform's ceiling. The default ceiling is 30 days; go over it and the pre-publish check says the wait can be at most 30 days and blocks publishing.
This is the most misunderstood part of the step, so let us be explicit.
Meta lets you send free-form messages for 24 hours from the person's last message. Once that runs out, only an approved template goes out on WhatsApp and nothing at all goes out on Instagram. That is a restriction on Meta's side and it applies to every tool that uses their interface.
The Wait step does not stop that clock. Wait 23 hours and the window is nearly closed; the message after the wait will not go out unless the person wrote again in the meantime.
⚠️ Note: A wait that reaches 23 hours raises a warning in the pre-publish check. On top of that, every message step pushed past 24 hours by the waits in front of it is warned about separately ("this message falls more than 24 hours after the person's last message"). The warning does not block publishing; the decision is yours.
If you need to say something after a long wait, there are two ways: use The Template step on WhatsApp, or put non-sending steps such as tagging and assignment after the wait instead of a message.
Without the person writing in between, at most 5 messages go out back to back; this is the safety net that stops a badly built flow from firing dozens of DMs at a customer.
The Wait step resets that counter. "Back to back" means without a break, and the wait you deliberately placed is a break. That way a multi-message flow spread over days (day 1, day 2, day 3) is not cut short even when the person never writes.
The reset also happens in the simulator, so the test does not behave differently from live.
Steps that return to each other without waiting for the person's reply are an error that blocks publishing: such a flow fires messages at somebody without pause. Adding a Wait step (or a step that waits for a reply) to the loop removes that error.
But be careful: waiting makes a loop safe, it does not make it finite. There is a separate limit on how many times the same node may run in one turn, and the wait does not reset it.
In the simulator on the Test tab, waits are skipped. You cannot sit through a three-day wait; the simulator records the step as waited (skipped) and moves to the next one.
That lets you see the whole logic of a flow in minutes. To confirm waits really work in live use, look at the Runs tab: the line says how long the wait lasted.
A publisher wants a three-day sequence for people who show interest in a book launch.
book to the Start step.purchased tag? The True branch goes to an End step.⚠️ Note: The messages after steps 3 and 6 in this example run into the 24-hour window unless the person wrote in between. This sequence works on WhatsApp with a template, and on Instagram only if the person writes again — the check tells you so as a warning.
Thinking the wait stops the 24-hour clock. It does not. A message after a long wait usually does not go out.
Using a Wait step to wait for the person's reply. The Wait step only watches the clock. To wait for somebody to write, use the message step's Wait for a typed reply setting or the Collect information step.
Putting a wait in a loop and assuming the problem is solved. The wait removes the error but does not fix the logic: if the loop's condition never changes its value, the flow returns to the same place anyway.
Using very short waits. If you want a one-minute breath between messages, the message step's Wait before sending setting suits better; it works at the scale of seconds and goes out together with the typing indicator.
Writing a wait over the ceiling. Anything over 30 days cannot be published.
Thinking the step is broken because the simulator skips it. The simulator skips waits on purpose.
The whole 24-hour rule is covered in The 24-hour messaging window. For messages spread over days, a sequence may suit better than an automation: What is a sequence. Loop protection is explained in The automation stopped: loop protection.
A wait in the right place turns a flow from a bot into a conversation.
Was this article helpful?