Try flow logic
-
- UpdatedApr 22, 2024
- 2 minutes to read
- Washington DC
- Flow Designer
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 () 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.

Execution details

Flow and action error handling resources
- Flow and Action Error Handling Level 1: Retry and Action Error Evaluation - Workflow Automation CoE
- Flow and Action Error Handling Level 2: Flow Logic - Workflow Automation CoE
- Flow and Action Error Handling Level 3: Flow Error Handling - Workflow Automation CoE
- Flow and Action Error Handling Level 4: Good Practices and Summary - Workflow Automation CoE
On this page
Related Content
- Assign subflow outputs flow logic
Specify the data the subflow returns when it completes running. Use subflow output as data for a parent flow or as input for another process.
- Call a workflow flow logic
Run a published and active workflow from your flow. You can use the flow data as a workflow input. For example, you can specify the current record as a workflow input.
- Do the following until flow logic
Apply one or more actions repeatedly until an end condition is met. You can use the flow data to specify the end conditions.
- Do the following in parallel flow logic
Run actions and subflows in separate paths within an isolated flow logic block.
- Dynamic flows flow logic
Identify and run a flow or subflow dynamically by using runtime data. Build templates to provide expected inputs for dynamically called flows or subflows.
- End Flow flow logic
Stop running the current flow. Use End Flow within a branch of the flow to specify an exit condition. For example, end the flow when it reaches a specific If flow logic block.
- Exit Loop flow logic
Exit from a flow logic loop when the conditions of an If flow logic are met. Continue running the flow from the next step after the flow logic loop. This flow logic is also known as break.
- For Each flow logic
Apply one or more actions to each record in a list of records.
- Go back to flow logic
Return to a prior step in the flow to repeat a sequence of actions.
- If flow logic
Selectively apply one or more actions only when a list of conditions is met.
- Make a decision flow logic
You can use the decision table branching logic in situations where multiple conditional paths are required, as an alternative to nested If, Else If, or Else flow logic. For example, if you want to determine what kind of car insurance you need, you can add inputs such as your age, accident history, and car model to the decision table to determine a level of insurance coverage. This logic can save you time and present a more readable format than nested if conditions or switch case statements.
- Set Flow Variables flow logic
Assign a value to one or more flow variables, which store flow data as data pills. Access flow variable values by referring to their data pill.
- Skip Iteration flow logic
Skip the current iteration of a flow logic loop when the conditions of an If flow logic are met. Continue running the flow logic loop with the next item in the list. This flow logic is also known as continue.
- Wait for a duration flow logic
Use this flow logic to give your users time to act during automated processes or to wait for a specific date and time to complete actions.