Overview

Action node is used to internal or external web-hooks. In some cases, it is often required to configure time-out for API call made through the action node. This configuration allows workflow designers to configure time-outs at the action node level in order to ensure that workflow executions do not get stuck indefinitely waiting for responses.

The setting applies to both Synchronous and Asynchronous Action Nodes. A timed-out Action Node is categorised as "Failed."

Why is this important?

• Prevents Workflow Stalls: Prevents workflows from hanging indefinitely when an external API is slow or unavailable.
• Improved Reliability: Enhances the robustness of your workflows by handling API failures gracefully.
• Control Over Execution Time: Gives you control over the maximum execution time of your Action Nodes.

Steps

• Add action node on the workflow builder canvas.

• Within the action node you would find the configuration to set time-out period.

  

Important Considerations:

• API Response Time: Choose a Time-out value longer than the typical API response time.
• Error Handling: A timed-out Action Node will have a "Failed" status. Use Conditional Nodes to handle these events.
• Time-out Value Ranges: