Skip to main content
The Wait step suspends execution for a configurable duration, then resumes at the next step. Use it to delay follow-up actions, implement cooldowns, or schedule work after a fixed interval.
Wait step inspector showing Duration field

​
Inspector

The Wait step inspector has a single Duration field:
  • A number input (default: 1)
  • A unit dropdown: Seconds, Minutes (default), Hours, Days
Set the duration and click Save.

​
When to use it

​
Sync vs async behavior

A sync run that asks for longer fails, with a message telling you to run the workflow asynchronously. The total budget matters because a Wait inside a Loop body runs once per iteration: five three-second waits fit, six do not.
For agent tool workflows — which run synchronously during a live call — keep Wait durations very short or remove them entirely. The user is waiting on the line.

​
What lands in ctx

After the wait completes, the duration is recorded under the step’s id:

​
Considerations

  • Durations are from when the Wait step is reached, not from when the workflow started. Upstream step latency doesn’t shift the timer.
  • Check state after waiting. The real-world situation may have changed during the wait (e.g., the contact already replied). Verify current state in the next step rather than assuming nothing changed.
  • Don’t use Wait for periodic execution. Use a Timer trigger for recurring scheduled jobs instead of a long-running workflow with internal Waits.