Allow a flow to continue running when an error occurs within a flow logic block. Run a sequence of actions in response to errors within the flow logic block.

Inputs

Try flow logic does not have field inputs. Instead, it displays a plus (Add Action, Flow Logic, or Subflow after Icon) icon that enables you to add a sequence of actions, flow logic, or subflows to attempt to run and evaluate for errors. You can add multiple items to a Try block. When an error occurs, the flow runs the sequence of actions, flow logic, or subflows within the error section of the flow logic block.

Outputs

This flow logic has no outputs, but the actions, flow logic, and subflows within the Try block may have outputs. When an error occurs within the Try flow logic block, the failing action returns an action status of Completed (error caught). You can use this action status to determine which item failed and build conditional logic in the Catch block. For example, if a Create record action in the Try block has a status of Completed (Error caught), then run a Create record action in the Catch block that has different values.

Example: Create a Problem record for critical priority incidents

In this example, the flow attempts to send one of three possible notifications when a critical priority network incident is created. The flow first tries to send an SMS message, and if that fails, it tries to send a Connect message. If the Connect message fails, it sends an email.

Figure 1. Try flow logic for multiple notification methods
Example configuration of a Try flow logic block

Execution details

Figure 2. Try flow logic execution details
Sample execution details of a Try flow logic block

Flow and action error handling resources