Delay
A Delay node waits for a fixed time, then lets the run continue. The wait is durable: nothing keeps running while it lasts, and the run picks up after it even if the platform restarts in between.
Settings
Section titled “Settings”| Field | What it does |
|---|---|
| Wait for | How long to wait, in the unit below |
| Unit | Seconds, Minutes or Hours |
A new Delay waits 3 seconds. A value under 1 is marked on the canvas. The wait is the same on every run; it can’t come from a variable.
In a run
Section titled “In a run”The step stays running for the length of the wait, then turns done. Other branches of the workflow keep going while one branch waits. While the whole run is asleep, its status reads waiting.
A waiting run still counts once against your plan’s monthly runs, however long it waits. It also keeps the version it started with: publishing during a long wait changes the next runs, not this one.
The Delay passes on the text it received, so the next step’s {{ input }} is the same as the
Delay’s. Read an earlier step’s fields as {{ nodes.<id>.<field> }}.
Output
Section titled “Output”| Field | What it holds |
|---|---|
waitedMs |
The wait, in milliseconds |
Example
Section titled “Example”The Order router template holds large orders for review before recording them: its Decision sends orders of 500 or more through a Delay named “Hold for review”, and smaller orders straight on.