Blocks
Wait
Pause workflow execution for a specified time delay
The Wait block pauses your workflow for a set amount of time before continuing. Use it when a downstream system needs a moment to catch up — a record to finish indexing, a file to finish processing, a rate limit to reset.
It performs a simple sleep for the configured duration. Nothing else happens while it waits.
Configuration
The maximum wait is 600 seconds (10 minutes). For longer or event-driven pauses, use a trigger to resume the workflow instead of holding an execution open.
| Field | Description |
|---|---|
| Wait Amount | How long to pause. Must be a positive number. Defaults to 10. |
| Unit | Seconds or Minutes. Defaults to Seconds. |
Outputs
| Output | Type | Description |
|---|---|---|
waitDuration | number | The configured duration, in milliseconds -- always the value you set, not a measured elapsed time. |
status | string | One of waiting or completed. |
Reference these downstream the same way as any other block output, for example
<wait1.waitDuration>.
Notes
- A wait is not actually interruptible on the server: cancelling a workflow marks the run cancelled, but the Wait block's own timer keeps running to completion regardless and always reports
completed-- it never reports acancelledstatus. - The block holds the execution open for its whole duration, so it counts toward the workflow's overall runtime. Prefer a trigger over a long wait when you are pausing for an external event.