You are here:
Handle Stage Errors in Orchestrations
Configure fault paths to manage stage errors in orchestrations. Add elements and Go To connectors that run when a stage or its steps encounter errors. These paths help orchestrations complete successfully instead of failing.
Required Editions
| View supported editions for Flow Orchestration. |
| User Permissions Needed | |
|---|---|
| To open, edit, or create an orchestration in Flow Builder: | Manage Flow |
To understand the value of and strategies for error handling in orchestrations, see Error Handling in Orchestrations.
Add a Fault Path
Define a fault path for a stage in the orchestration.
This task requires an orchestration with at least 1 stage.
- Hover over a stage in the orchestration.
-
Click
, and then select Add Fault Path.
- Save your work.
Add at least 1 element to the fault path.
Add a Decision Element to a Fault Path
Use decision elements to create conditions that control what elements run in a fault path.
This task requires an orchestration with at least 1 stage that has a defined fault path.
Use a Decision element to determine which step encountered an error and route the orchestration to the appropriate recovery action. Decision elements evaluate orchestration run variables and automatic output to identify the error's source and determine the best recovery path.
When implementing a centralized fault path strategy, the Decision element serves as the entry point. It identifies which stage caused the error and routes to the appropriate outcome path for resolution.
-
In the Fault Path, click
, and then select Decision.
- Enter a label, API name, and description.
-
Select the type of decision logic to use for the Decision element.
- To determine which outcome runs based on traditional logic expressions and explicitly defined data from your orchestration, select Define Manually (Default)
- To dynamically determine which outcome runs based on AI evaluating data from your orchestration, select Define with AI (Advanced).
-
If you selected Define Manually (Default), define the conditions and outcomes for the
element. Outcomes for a Decision element with manual conditions are evaluated in the
order that they’re listed. Therefore, the order that you define your outcomes in can
impact the outcome that the orchestration run takes.
- Enter a label and an outcome API name. The outcome API name must be unique within the orchestration
-
Define the condition requirements to use for the first outcome.
Option Behavior for Decision Outcomes All Conditions Are Met If one of the conditions is false, the orchestration evaluates the next outcome’s conditions. Any Condition Is Met If one of the conditions is true, the orchestration immediately takes this outcome’s path. Custom Condition Logic Is Met If you select this option, provide the condition logic by entering up to 1,000 characters. Use:
- Numbers to refer to each condition
- AND, OR, or NOT to identify which combination of conditions must be true
- Parentheses to group parts of the string together
If you enter AND, it’s the same as if you selected All Conditions Are Met. If you enter OR, it’s the same as if you selected Any Condition Is Met. If you enter any other logic, make sure that you include a number for each condition.
For example, for 1 AND NOT(2 OR 3), the flow evaluates whether the first condition is
trueand neither the second nor third condition istrue. -
Define the logic conditions for the first outcome.
Column Header Description Resource - Select an input variable or automatic output from a stage or step.
- Select a Decision element.
- Select a global variable.
Operator The available operators depend on the data type selected for Resource. See Flow Orchestration Operators in Decision Elements. Value Resource and Value in the same row must have compatible data types.
- Select an orchestration resource, such as an input variable or automatic output from a stage or step.
- Select a global variable.
- Enter a literal value.
When you add or subtract a number from a date value, the date adjusts in days, not hours.
-
If you selected Define with AI (Advanced), define the instructions and outcomes for
the element.
- For Decision Instructions, enter text that describes what decision the element makes. Include resources from the orchestration to improve AI accuracy.
- Enter a label and an outcome API name. The outcome API name must be unique within the orchestration.
- For Outcome Instructions, enter text that tells AI when to take the outcome. Include resources from the orchestration to improve AI accuracy. Outcomes for a Decision element with AI conditions are evaluated simultaneously. Therefore, the order that you define your outcomes in has no impact on the outcome that the orchestration run takes.
-
(Optional) To add a decision outcome to a Decision element, click
. Repeat the steps to add a label and outcome API name, set up conditions, and
identify logic between the conditions. For manual conditions, see Step 4b. For AI
conditions, see Step 5b.
-
(Optional) To reorder a decision outcome in a Decision element, click
and drag the item to its new location. You can’t move a decision outcome with
conditions to the last position on the list because the default outcome is always
last.
-
(Optional) To improve the readability of the Decision element, rename the default
outcome.
- Under Outcome Order, select Default Outcome.
- Enter a label.
- Save your work.
