Wait For Executions
AI-generatedOverview
This node waits for sub-workflow executions to complete before proceeding. It is useful in scenarios where a workflow depends on the results of other workflows and needs to pause until those executions finish. For example, it can be used to synchronize multiple asynchronous processes by waiting for their completion before continuing.
Use Case Examples
- Waiting for a sub-workflow execution to finish before processing its results.
- Retrying a sub-workflow execution status check multiple times until it completes or fails.
Properties
| Name | Meaning |
|---|---|
| Wait (Seconds) | Number of seconds to wait before re-checking the status of executions. |
| Retry Limit | Maximum number of retries before considering an execution failed. Set to 0 for infinite retries. |
| Execution Timeout (Seconds) | Maximum execution time before considering an execution failed. Set to 0 to ignore. |
Output
JSON
execution_id- The ID of the sub-workflow execution being waited on.execution_output- The output or error details of the sub-workflow execution once it completes or fails.
Dependencies
- Requires an API key credential for accessing the n8n API to check execution statuses.
Troubleshooting
- If no execution ID is found in the input data or metadata, the node will fail with an error indicating the missing execution ID.
- If the execution ID does not correspond to a valid execution, the node will fail with an error indicating the execution was not found.
- If the retry limit is exceeded while executions are still processing, the node will fail those executions with a retry limit exceeded error.
- If the execution timeout is set and exceeded, the node will fail the execution with a timeout error.