Node-level Timeouts
- 23 Aug 2024
- 1 Minute to read
- Contributors
- Print
- DarkLight
- PDF
Node-level Timeouts
- Updated on 23 Aug 2024
- 1 Minute to read
- Contributors
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
We have included an Interactive Training to provide a more engaging and visual learning experience. End users are required to complete their training through the CSG University.
Individual nodes used in a graph can become slow during execution time when resources are constrained. Eventually, those nodes may use up the entire time allotted for job execution.
If this occurs, job queues may start to back up. The way Xponent handles this to avoid having further delays and backed-up queues is by setting node-level timeouts.
When a node times out, an error will go down an error branch, providing visibility to users on the timeout.
.png?sv=2022-11-02&spr=https&st=2024-09-22T21%3A32%3A59Z&se=2024-09-22T21%3A42%3A59Z&sr=c&sp=r&sig=x%2F0xVWD%2BtCz6JIA8Hw%2FSCxNLuv%2B8r7IlB37ks4NHwrQ%3D)
In addition to the node-level timeouts, the graph execution also has a timeout threshold. An error goes down to the error branch after reaching the defined threshold.
Avoiding timeouts
To ensure optimal use of resources, we have implemented node-level and graph timeouts as safety measures.
It is crucial to keep in mind that adhering to recommended graph design practices is the most effective way to prevent timeouts from occurring.
Is it helpful? React and share your comment
