Delay Execution¶
Pauses the current branch of a workflow for a specified number of seconds, then forwards the provided data unchanged. Supports fractional seconds for sub-second waits. Useful for pacing, synchronization, or rate-limiting steps.
Usage¶
Insert this node between two steps when you need to wait before continuing (e.g., spacing out API calls, giving time for external processes, or coordinating concurrent branches). Set the delay in seconds; connect any upstream data to have it forwarded after the wait.
Inputs¶
| Field | Required | Type | Description | Example |
|---|---|---|---|---|
| delay | True | FLOAT | Number of seconds to wait before forwarding data. Supports fractional values for sub-second delays. | 2.5 |
| input | False | WILDCARD | Any data to pass through after the delay. The node does not modify this data. | Upstream data object to be delayed (e.g., an image, text, or structured payload) |
Outputs¶
| Field | Type | Description | Example |
|---|---|---|---|
| output | WILDCARD | The same data that was provided to the input, emitted after the delay completes. | Same object/value received at input |
Important Notes¶
- This node blocks its downstream execution for the specified duration; the rest of the workflow branch resumes only after the delay completes.
- Fractional seconds are supported (e.g., 0.1 for 100 ms). Actual timing precision depends on the operating system and system load.
- Providing a negative delay will cause an error from the underlying timing system.
- If no input is connected, the node will output an empty/null value after the delay.
- Long delays will increase total workflow runtime; use with care in time-sensitive pipelines.
Troubleshooting¶
- Node seems stuck or slow: It is likely waiting for the configured delay. Reduce the delay value to speed up execution.
- No output received: Ensure the input is connected. Without an input, the node forwards a null/empty output after waiting.
- Error about delay value: Use a non-negative float for the delay (e.g., 0, 0.5, 3). Negative values are not allowed.
- Downstream steps start too early: Place this node directly before the steps you need to pause to ensure they are gated by the delay.