Manage errors

While developing and executing flows, users may encounter two different kinds of errors, design time and run time errors.

The design time errors are associated with the configuration of the deployed actions. This kind of error appears while developing the flow and prevent it from running. An empty mandatory field or the use of an undefined variable may cause this kind of error.

Screenshot of a design time error.

The run time errors or exceptions come up when the flow is running. These errors cause the flow to fail unless an exception handling behavior has been set. An invalid file path can cause this kind of error.

Screenshot of a run time error.

When an action throws an error, the platform displays an error icon next to it and a pop-up pane with relevant error information.

The Errors pane is split into three columns:

  • Subflow: The name of the subflow containing the action that threw the error.
  • Action: The line number of the action that threw the error.
  • Error: The error message.

If the occurred error is a design time error, the platform also displays a short description of the error inside the action.

Screenshot of an error description inside an action.

To implement an error handling behavior in your flow, you can use the Get last error action to retrieve the latest occurred error and use it in later actions.

The Get last error action returns an error type variable that provides six different properties: the name, the location and the index of the action that failed, the subflow that contains this action, and the details and the message of the action.

To avoid retrieving the same error value later in your flow, enable the Clear error option that clears the last error after storing it in the variable.

Screenshot of the Get last error action.

The error detail view

To find more information about a thrown exception, navigate to the Errors pane and double-click on the respective error. Once you do so, the Error details dialog box will appear. This dialog box displays information about:

  1. Location: The subflow and the action that threw the error.
  2. Error message: The error message.
  3. Error details: A long description of the error. These details give a clear message about why the error happened and what the cause is.

Screenshot of the Error details dialog box.