Delay Execution¶
Pauses the workflow for a specified number of seconds, then forwards the provided input unchanged. Supports fractional seconds for sub-second delays and accepts any data type as passthrough input.
Usage¶
Use this node when you need to intentionally delay progression in a workflow—such as pacing requests to external services, coordinating timing with other processes, or inserting short pauses between steps. Place it inline where the output should be delayed before reaching downstream nodes.
Inputs¶
| Field | Required | Type | Description | Example |
|---|---|---|---|---|
| delay | True | FLOAT | Number of seconds to wait before forwarding the input. Supports fractional values for sub-second precision. | 2.5 |
| input | False | WILDCARD | Any data to pass through after the delay completes. If not provided, the node outputs null. | Any data type (e.g., an image object, text string, JSON payload) |
Outputs¶
| Field | Type | Description | Example |
|---|---|---|---|
| output | WILDCARD | The same data received on the input, forwarded after the delay period. If no input was provided, outputs null. | Same as the provided input, unchanged |
Important Notes¶
- This node blocks execution for the specified time; downstream nodes will not run until the delay completes.
- Fractional seconds are supported (e.g., 0.001 for 1 millisecond).
- If no input is connected, the output will be null.
- Negative delays are invalid and will cause an error.
- Large delays will hold resources for the duration of the wait.
Troubleshooting¶
- Delay has no effect: Ensure the delay value is greater than zero.
- Workflow seems stuck: Verify the delay isn't set to an unexpectedly large value.
- Downstream node errors on null: Provide an input or handle null outputs when no input is connected.
- Error about sleep value: Use a non-negative numeric value for the delay (e.g., 0 or greater).