The Wait block delays the next step. Choose an inline wait for seconds or a few minutes, or enable Async to suspend the run and resume later.
Space out requests
A two-second wait spaces the two API requests apart. It can also sit between polling attempts. Account for other branches and workflow runs when calculating an API's rate limit.
Configuration
| Field | Behavior |
|---|---|
| Wait Amount | Positive duration. Defaults to 10. |
| Unit | Seconds or Minutes with Async off; Minutes, Hours, or Days with Async on. |
| Async | Off: wait in the running execution, up to 5 minutes. On: suspend and schedule resumption, up to 30 days. |
Async always suspends the run, even for a short duration. The resume poller picks it up after the scheduled time, so resumeAt is not an exact execution-time guarantee. Self-hosted deployments need their resume scheduler configured for automatic resumption.
Outputs
| Reference | Value |
|---|---|
<wait.status> | waiting for a suspended wait, completed for a finished inline wait, or cancelled when an inline wait is interrupted |
<wait.waitDuration> | Requested duration in milliseconds |
<wait.resumeAt> | Scheduled ISO resume timestamp for an async wait |
Stopping a run cancels an active wait. A delay extends the workflow's wall-clock completion time; log duration and resumed execution records describe execution separately.
Send a delayed follow-up
Enable Async and select two days to suspend the run before the follow-up step. Configure that step's messaging tool to send the notification.