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
| Name | Type | Required | Description |
|---|---|---|---|
delay_seconds | number | No | Optional override for delay duration from upstream node |
data | any | No | Passthrough data forwarded after the delay |
Output ports
| Name | Type | Required | Description |
|---|---|---|---|
result | json | No | Delay metadata: delayed (bool), delay_seconds, actual_seconds |
passthrough | json | No | Original input data passed through unchanged |
success | boolean | No | Whether the delay completed without cancellation |
Settings
Basic
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Delay (seconds) | delay_seconds | number | No | 1 | min 0; max 3600 | Duration to pause in seconds |
Errors
| Code | Description |
|---|---|
CONTEXT_CANCELLED | Pipeline 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.
Quelque chose n'est pas clair ? Envoyez vos commentaires sur la documentation par courriel.