Skip to main content

Delay

Category: Control
Node id: delay

Pauses pipeline execution for a configurable duration with context cancellation support

What it does​

  • Configurable pause duration up to 1 hour
  • Context cancellation support for graceful shutdown
  • Input-driven delay override from upstream nodes
  • Data passthrough during delay

Use cases​

  • Rate-limit API calls between pipeline steps
  • Add cooldown periods between retry attempts
  • Throttle batch processing to avoid overloading downstream systems

Runtime​

  • Performance tier: variable

Input ports​

NameTypeRequiredDescription
delay_secondsnumberNoOptional override for delay duration from upstream node
dataanyNoPassthrough data forwarded after the delay

Output ports​

NameTypeRequiredDescription
resultjsonNoDelay metadata: delayed (bool), delay_seconds, actual_seconds
passthroughjsonNoOriginal input data passed through unchanged
successbooleanNoWhether the delay completed without cancellation

Settings​

Basic​

SettingNameTypeRequiredDefaultAllowed valuesDescription
Delay (seconds)delay_secondsnumberNo1min 0; max 3600Duration to pause in seconds

Errors​

CodeDescription
CONTEXT_CANCELLEDPipeline was cancelled during the delay period

Runtime notes​

  • All inputs are forwarded as-is via the 'passthrough' output — wire downstream nodes to passthrough, not result
  • Values above 3600 seconds are silently capped to 3600 (1 hour)
  • If delay_seconds is 0, no delay occurs and delayed=false in result
  • Pipeline cancellation during the delay returns an error, not a partial result

See Build any workflow for how to put nodes together and Ports, types and data flow for how port types connect.

Something unclear? Send documentation feedback by email.