Skip to main content
Node ReferenceDelay Node

Delay Node

Pause workflow execution for a specified duration.

The Delay node is a planned logic node for pausing workflow execution for a specified duration before downstream nodes continue. It is designed to introduce a timed wait inside a running graph.

Not yet available
The Delay node is part of the planned logic-node set. It appears in the node reference catalog with its intended purpose, but it is not wired into Builder Studio execution yet. There is no Delay node type, canvas node, executor, or schema definition in the current product, so it cannot be added to a canvas or run today. This page documents the intended behavior so the contract is clear before the node ships.

Intended purpose

Delay is meant to pause workflow execution for a specified duration. When a Delay node runs, downstream nodes would not start until the timer elapses, letting you space out steps, wait between external calls, or give an asynchronous side effect time to settle. It belongs to the logic and control group, alongside Conditional, Merge, and Loop.

How timing works today

Builder Studio already runs some steps as durable, suspendable operations: long-running provider work, such as video generation, parks on a waitpoint and resumes when the result is ready rather than blocking the worker. A Delay node would reuse this style of durable wait, but with a fixed duration as the resume condition instead of an external result. Today there is no node that simply waits a set amount of time; pauses only happen implicitly while a provider step is in flight.

What to use instead for now
Until the Delay node ships, there is no canvas control for inserting a fixed pause between steps. If you need to wait on external work, model that work as the node that produces the result you are waiting for rather than as a standalone timer.

Related pages

Was this page helpful?