Skip to main content
Node type: delay · Version: 1 · Category: Logic Wait without blocking the runner. This node is not marked with the catalogue’s generic side-effect flag. That classification is not a guarantee that every configured operation is read-only; review the concrete action and its destination.

​
When to use this node

  • Pause briefly between actions when an external system needs processing time.
  • Rate-space a sequence without occupying a blocking thread.

​
Example: Wait before checking an export

Pause for 30 seconds after requesting an export, then continue to the status check.
Example settings
This shows the important settings, not a complete exported node.
  1. Place Delay after the request that starts the remote work.
  2. Choose seconds or minutes and a non-negative amount.
  3. Follow it with an explicit status check rather than assuming the work completed.

​
Configuration

​
Workflow JSON

The editor stores this node with the following implemented default configuration:
Default node configuration
Values may be entered literally or mapped from an earlier compatible output when the inspector exposes a mapping control. See Variables and data mapping.

​
Inputs

This node has no typed ports in this direction.

​
Outputs

​
Execution behavior

  • The wait is cancellable and returns delayedMs when it completes.
  • Delay waits once; it is not a retry loop or a page-readiness assertion.
  • The editor catalogue declares result (any) for mapping. The execution inspector can contain additional evidence fields; inspect a real result before selecting nested paths from object or any outputs.

​
Common issues

  • Prefer Wait For for browser state because fixed delays are sensitive to page speed.
  • Long delays keep an execution active and count toward the relevant execution and session limits.

​
Where it can run

  • Desktop local runner
  • Paired self-hosted runner
  • Hosted runner

​
Test and inspect

Use Test node in the editor to preview this step with the current configuration. A full run records resolved inputs, outputs, logs, duration, and any artifacts in the execution inspector. Side-effecting or destructive nodes can require an additional confirmation or approved workflow permission.