Timeout in the Pipeline Executor connector
Learn how to avoid this error in synchronous requests.
PreviousHow to resolve Error 409: “You cannot update a pipeline that is not on draft mode”NextDigibee Customer Support
Last updated
Learn how to avoid this error in synchronous requests.
Last updated
In synchronous operations of the Pipeline Executor connector, an origin pipeline is triggered while the destination pipeline waits for its completion and response to proceed.
In this case, a desynchronization in communication between the two pipelines may occur, depending on the deployment configuration of both, especially when there is a high volume of executions. The destination pipeline returns a timeout error to the source pipeline, even if it’s executed in time.
This happens when the number of calls exceeds the processing capacity of the destination pipeline and may result in a timeout error as shown below:
If this situation occurs, check if the flows involved fit into one of the following scenarios:
Ensure the number of concurrent executions of the destination pipeline is increased to handle more requests — this may require an increasing the number of replicas.
If the operation can be asynchronous, change it accordingly or consider using an event-based call so the queue manager can control traffic to the destination pipeline.
To fix the issue:
The origin pipeline is deployed with more simultaneous executions than the destination pipeline.
The destination pipeline is triggered by multiple flows at the same time, causing the number of requests to exceed the concurrent executions allowed in its deployment.
