Delay Execution¶
Pauses workflow execution for a specified number of seconds, then forwards the input unchanged. Accepts any data type and simply delays its passage downstream. Useful for timing control and coordinating steps that require a pause.
Usage¶
Use this node when you need to introduce a timed pause in a workflow—such as rate limiting, synchronization with external processes, or staging multi-step operations. Set the delay in seconds (fractions allowed) and optionally pass any data through; it will be emitted after the delay.
Inputs¶
| Field | Required | Type | Description | Example |
|---|---|---|---|---|
| delay | True | FLOAT | Number of seconds to wait before forwarding the input. Supports fractional values for sub-second delays. | 2.5 |
| input | False | WILDCARD | Any data to pass through after the delay (e.g., image, text, number, or structured data). If not provided, the node outputs a null/empty value after waiting. | Any value (e.g., "Ready", 42, an image object, or a data payload) |
Outputs¶
| Field | Type | Description | Example |
|---|---|---|---|
| output | WILDCARD | The same data received on the input, emitted after the specified delay. If no input was provided, outputs a null/empty value. | Same as the provided input (e.g., "Ready", 42, image object) |
Important Notes¶
- Blocking behavior: This node blocks execution for the specified duration; downstream nodes will wait until the delay finishes.
- Fractional seconds supported: Use values like 0.5 for half a second or 0.001 for one millisecond.
- No transformation: The data is not modified—it's forwarded as-is after the delay.
- Empty output if no input: If the input is not connected, the node still waits and then outputs a null/empty value.
- Timing precision: Very small delays may be limited by system timer resolution and are not guaranteed to be exact.
Troubleshooting¶
- Workflow appears stuck: Check the delay value; large numbers (e.g., 300) will pause execution for several minutes.
- No data after delay: Ensure the input is connected. When not connected, the node outputs a null/empty value after waiting.
- Delay not precise: Sub-millisecond or very small delays may not be accurate due to OS scheduling. Increase the delay or avoid extremely small values.
- Downstream timing issues: Remember this node is blocking; consider placing it only where a pause is acceptable for the entire branch.