The Wait block pauses a workflow for a set time, then continues. Use it to space out actions, respect API rate limits, or give an external system time to finish. A short wait runs in line; a long one suspends the run and resumes later.
Configuration
Wait Amount
The duration to pause, as a positive number.
Unit
The time unit. For a short, in-line wait, choose Seconds or Minutes. With Async on, choose Minutes, Hours, or Days.
Async
Off, the run sleeps in line for the duration (up to 5 minutes). On, the run suspends and resumes after the delay, which is what lets a wait run for hours or days without holding the execution open. A suspended wait records when it will resume in <wait.resumeAt>.
Outputs
| Output | What it is |
|---|---|
<wait.status> | waiting, completed, or cancelled |
<wait.waitDuration> | The wait duration, in milliseconds |
<wait.resumeAt> | ISO timestamp a suspended (async) wait resumes at |
Examples
Space out API calls
A short wait between two calls keeps the workflow under an API's rate limit. The same shape works for polling: wait, then re-check an external job.
Send a delayed follow-up
With Async on, the run suspends for two days and resumes to send the follow-up, without holding the execution open in between.
Best Practices
- Use a short in-line wait for seconds to a few minutes. Turn on Async for hours or days so the run doesn't stay open the whole time.
- Remember waits extend the run. The wait counts toward total duration, which shows in the logs.
- A wait is cancellable. Stopping the run cancels an active wait, and
statusreportscancelled.