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.
Press enter or space to select a node.You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.
Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.
Off, the run sleeps in line for the duration (up to 10 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>.
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 status reports cancelled.
Common Questions
An in-line (synchronous) wait is capped at 10 minutes. For longer delays, turn on Async: the run suspends and resumes after the delay, so a wait can run for minutes, hours, or days.
Yes. Waits are interruptible by workflow cancellation. If the run is stopped while a Wait is active, the wait is cancelled and the status output reads 'cancelled'.
A sync wait (Async off) sleeps in line for up to 10 minutes while the execution stays open. An async wait (Async on) suspends the run and resumes after minutes, hours, or days, recording the resume time in <wait.resumeAt>.
An in-line wait performs a simple sleep and does not actively use compute, though the execution stays open. An async wait suspends the run entirely, so nothing is held open until it resumes.
waitDuration (the wait in milliseconds), status ('waiting', 'completed', or 'cancelled'), and resumeAt (the ISO timestamp an async wait resumes at).