Workflow node reference

Delay

Wait before continuing. Exact configuration, outputs, execution behavior, errors, limits, and examples for the Delay workflow node.

Automation buildersIntermediateAvailable

What this guide covers

Category: Logic.
Use it to wait a fixed number of seconds, minutes, hours, or days inside one execution.
2 configuration fields and 4 documented outputs.
Delay is relative to when the node runs and has no weekday, business-hours, start-date, or end-date calendar controls.

What this node does

Wait before continuing

Use it to wait a fixed number of seconds, minutes, hours, or days inside one execution.

When not to use it

Do not use it as a recurring calendar. Use the Scheduled trigger for daily, weekly, or monthly starts.

Prerequisites

Duration of at least 1
A supported unit
A valid downstream connection

Check before configuration

Duration of at least 1. A supported unit. A valid downstream connection

Inputs and configuration fields

Delay configuration fields
Field	Key	Control / type	Requirement	Default	Accepted values and behavior
`Duration`	duration	number	Required when shown	No default	minimum 1
`Unit`	unit	select	Optional	minutes	Seconds (seconds), Minutes (minutes), Hours (hours), Days (days)

Configure the node

Drag Delay from Logic in the node palette.
Select the node to open its configuration drawer.
Complete every required field and any conditional field revealed by your choices.
Insert variables only from the current trigger or an earlier node on the same path.
Connect every required output handle to the intended next step.
Save and run Workflow Test with representative data before activation.

Outputs

Later nodes can use these values only after this node has run successfully on the same execution path.

Delay output variables
Variable	Type	Meaning
`{{nodes.delay.delay_ms}}`	number	Configured delay in milliseconds
`{{nodes.delay.waited_until}}`	string	When an inline delay completed
`{{nodes.delay.resume_at}}`	string	When a scheduled delay should resume
`{{nodes.delay.inline}}`	boolean	Whether the delay ran inline

Execution behavior

Calculates the delay in milliseconds.
Short waits may complete inline; longer waits expose a resume time for scheduled continuation.
The workflow continues after the wait completes.

Retries and usage

Do not assume a failed node is automatically retried. Review the execution result and the relevant service documentation before repeating an operation that could create a duplicate side effect.

Example use case

Wait two hours before sending a follow-up in the same customer execution.

Complete workflow pattern

text

New Conversation → Send Text → Delay → Condition → Send Text

Common errors

Delay common errors
Symptom	Resolution
`Duration is invalid`	Enter a number of at least 1.
`Follow-up never runs`	Inspect the execution and confirm the workflow/resource was not archived while waiting.

Limitations

Delay is relative to when the node runs and has no weekday, business-hours, start-date, or end-date calendar controls.

Current product limits

Delay is relative to when the node runs and has no weekday, business-hours, start-date, or end-date calendar controls.

Run a workflow on a scheduleConfigure a Scheduled trigger for once, daily, weekly, or monthly workflow starts.Scheduler overviewChoose between Yanola's one-time Scheduler and the once, daily, weekly, or monthly Scheduled workflow trigger.End FlowEnd the workflow execution. Exact configuration, outputs, execution behavior, errors, limits, and examples for the End Flow workflow node.

Related documentation