Building a Flow
      Back to home
      1. Knowledge Base
      2. Flows
      3. Building a Flow

      Flows Error Handling

      When Flows interact with third-party systems via HTTP requests, errors may occur. Learn to utilize error-handling options to improve your Flows management.

      This article covers the following topics:

      Overview

      A Flow may occasionally encounter issues, such as being unable to locate the required data or facing incorrect data formats. In such cases, the default behavior is for the entire flow to halt, and the error will be logged for review.

      When an error arises, the Flow will automatically stop at the affected step, and the error details will be recorded in the History tab.

      The Error Handler functionality allows you to define the response to errors that occur at specific steps. It is important to note that for receiving applications (action steps within your Flows), the Error Handler is designed to manage only external errors from other linked apps.

      In instances of timeout issues or internal errors related to Flows, the Error Handler will not be effective, and the step in question will still be marked as an error.

      Note: It will only be possible to restart the Flow manually after fixing errors.

       

      How do I access the error-handling options?

      Once you have accessed a Flow that you have created, you can find the error-handling options for each step located on the right-hand side within the ellipsis dropdown menu:

      errorhandling3

       

      Error Types

      • Partner (app) error: This type of error arises when Flows attempts to make an outgoing HTTP request to an application, but the application indicates that the request is invalid. In such cases, the application will respond with an error message detailing the issue.

      • Timeout error:  This error arises when Flows does not receive a response to its request. By default, Flows will wait for a period of 10 seconds to receive a response and, if none is received, it will log an error message stating:

        "Request for ## timed out. This type of error automatically resends data and assigns penalty points to the automation."

      • Connection error: This error occurs when Flows is unable to connect to a server, which may happen if a third-party system is experiencing failure or if its servers are currently unavailable. In such situations, an error message will be displayed indicating the connection issue: "Failed to establish a connection with "

       

      Choose What To Do When Errors Occur

      In the error handler modal, you can choose from three available options to determine how your Flow should respond when errors arise in your steps:

      • Stop the flow: In the event of an error at this step, the Flow will cease all steps entirely.
      • Continue the flow: All errors in the step will be ignored, and the Flow will proceed to the next step.
      • Move on to the selected step below: If an error occurs at this step, the Flow will proceed to execute the step that you have selected from the dropdown list.

      errorhandling4

      Manual Errors Resending

      You have the option to manually restart each step with an error; however, please be aware that this will result in the re-transfer of all data. If you have made any edits to the step settings following the initial error, those updated settings will be included in the resend of the request (action).

      For this mechanism to function correctly, the position of the step must remain unchanged after the error has occurred. To initiate a manual resend of the request (action), navigate to the History tab for the Flow and select the "Resend errors" button to proceed with the data transfer.

      resenderrorsbutton

      Upon clicking the button, the system will attempt to resend the data within a 5-minute timeframe. You will notice an additional note appearing in the same section of the log below. If there are subsequent steps following the erroneous step, those will also be executed during this process.

      Note: You can utilize the "Resend Errors" button unlimited times while the Flow continues to run.

      ​

      Automatic Errors Resending

      Only the Timeout Error type is eligible for automatic resending. In this scenario, Flows will treat the server as temporarily unavailable.

      When a Timeout Error occurs, Flows will attempt to resend the request up to five times, following these intervals:

      1. After 5 minutes

      2. After 15 minutes

      3. After 30 minutes

      4. After 60 minutes

      5. After another 60 minutes

      If the timeout issue persists beyond these attempts, the process will be halted. An email notification to the account owner will be sent once the fifth attempt is reached without success.