--- schema_version: "1" id: 64342cfefbe8ba36006a34a7798ab737b1d6e61a0feede2427758397b73a0b76 title: Handle Stage Errors in Orchestrations collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/orchestrator_add_error_handling.md canonical_url: https://help.salesforce.com/s/articleView?id=platform.orchestrator_add_error_handling.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: e97817cd3de4f8035346270303fad12e6862c6333a1c91e28a436d545e7314bf description: 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. products: - Flow Builder - Salesforce Platform release: "264" --- # 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](https://help.salesforce.com/s/articleView?id=platform.orchestrator_concepts_error_handling.htm&release=264.0.0&type=5 "Error handling manages unexpected issues that occur in stages during an orchestration run. Configure fault paths for stages to define recovery actions when stage errors occur, ensuring orchestrations complete successfully instead of failing."). ## Add a Fault Path Define a fault path for a stage in the orchestration. This task requires an orchestration with at least 1 stage. 1. Hover over a stage in the orchestration. 2. Click ![The actions icon](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/platform_automation/images/actions_icon.png), and then select **Add Fault Path**. 3. 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. 1. In the Fault Path, click ![Add element](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/platform_automation/images/orchestration/orchestrator_fbuilder_circleplus.png), and then select **Decision**. 2. Enter a label, API name, and description. 3. 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)**. 4. 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. 1. Enter a label and an outcome API name. The outcome API name must be unique within the orchestration 2. 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.

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 `true` and neither the second nor third condition is `true`.

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 true and neither the second nor third condition is true.

3. Define the logic conditions for the first outcome.

Column Header	Description
Resource	Options: 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. Options: 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.

Column Header

Description

Resource

Options:

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.

Options:

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.

5. If you selected Define with AI (Advanced), define the instructions and outcomes for the element. 1. For Decision Instructions, enter text that describes what decision the element makes. Include resources from the orchestration to improve AI accuracy. 2. Enter a label and an outcome API name. The outcome API name must be unique within the orchestration. 3. 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. 6. (Optional) To add a decision outcome to a Decision element, click ![The new outcome button](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/platform_automation/images/decision_element_add_outcome_button.png). 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. 7. (Optional) To reorder a decision outcome in a Decision element, click ![The reorder icon for a decision outcome](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/platform_automation/images/decision_outcome_reorder_icon.png) 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. 8. (Optional) To improve the readability of the Decision element, rename the default outcome. 1. Under Outcome Order, select **Default Outcome**. 2. Enter a label. 9. Save your work.