--- schema_version: "1" id: b27943f4afe1c3634afda68bd6e9e5b10aa9b5a033c5a9d1e05865e86d1745a7 title: Customize What Happens When a Flow Fails collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/flow_build_logic_fault.md canonical_url: https://help.salesforce.com/s/articleView?id=platform.flow_build_logic_fault.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 7e9121701139bcae99c6987535b17396b202507624171ac0cde907e2484aa004 description: Learn how fault paths customize what happens when a flow fails. Choose how to notify admins, guide users, and take a follow-up action. products: - Flow Builder - Salesforce Platform release: "264" --- # Customize What Happens When a Flow Fails Learn how fault paths customize what happens when a flow fails. Choose how to notify admins, guide users, and take a follow-up action. ### Required Editions
View supported editions.
## How Fault Paths Work Your flow fails when Salesforce can’t complete a database operation. A validation rule or a missing required value can prevent the operation from completing. Add fault paths to elements or actions that perform database operations. Examples include the Update Records element and the Submit for Approval core action. A fault path customizes what happens when an error occurs. A fault path is an alternate route that a flow follows when an element encounters an error. Use a fault path to decide what happens after an error. You can notify an admin or show a message to the person running the flow. You can also take a follow-up action. If an element has no fault path, or its fault path is empty, Salesforce uses the default error-handling behavior. That behavior varies by flow type and can affect whether Salesforce rolls back the transaction. For more information, see [Default Flow Error Handling](https://help.salesforce.com/s/articleView?id=platform.flow_build_logic_fault_default.htm&release=264.0.0&type=5 "Understand how flows behave when they fail to help you decide on error handling strategies. Learn what happens by default so you can determine if you need custom error handling for your specific use case."). ## Choose How to Respond to Flow Errors When you plan error handling for a flow, decide how Salesforce responds to the error and who needs information about it. - Learn the default behavior for the flow type and decide whether to add a fault path. - Choose who receives fault emails. See [Select Flow and Process Error Email Recipients](https://help.salesforce.com/s/articleView?id=platform.flow_troubleshoot_error_email.htm&release=264.0.0&type=5 "When a process or flow interview fails, a detailed email is sent to the admin who last modified the process or flow. However, sometimes the admin isn’t the best person to act on the details of what ran and what went wrong. In that case, you can send error emails to the Apex exception email recipients."). - Send diagnostic information from a fault path. See [Configure Every Fault Path to Send You an Email](https://help.salesforce.com/s/articleView?id=platform.flow_build_logic_fault_email.htm&release=264.0.0&type=5 "As a best practice, we recommend configuring the fault connectors in your flow so that you always receive an email when a flow fails. In the email, include the current values of all your flow’s resources. The resource values can give you insight into why the flow failed."). - Show a helpful message to people running screen flows. See [Customize the Error Message for Running Flow Users](https://help.salesforce.com/s/articleView?id=platform.flow_build_logic_fault_usermsg.htm&release=264.0.0&type=5 "Add a fault path to a screen flow to show a helpful message when an element fails."). - Take another follow-up action, such as asking for corrected information or creating a case. See [Other Examples of Error Handling in Flows](https://help.salesforce.com/s/articleView?id=platform.flow_build_logic_fault_examples.htm&release=264.0.0&type=5 "Examples of using fault connectors to handle flow errors include requesting corrections from the user and bypassing the error."). - **[Default Flow Error Handling](https://help.salesforce.com/s/articleView?id=platform.flow_build_logic_fault_default.htm&release=264.0.0&type=5)** Understand how flows behave when they fail to help you decide on error handling strategies. Learn what happens by default so you can determine if you need custom error handling for your specific use case. - **[Select Flow and Process Error Email Recipients](https://help.salesforce.com/s/articleView?id=platform.flow_troubleshoot_error_email.htm&release=264.0.0&type=5)** When a process or flow interview fails, a detailed email is sent to the admin who last modified the process or flow. However, sometimes the admin isn’t the best person to act on the details of what ran and what went wrong. In that case, you can send error emails to the Apex exception email recipients. - **[Configure Every Fault Path to Send You an Email](https://help.salesforce.com/s/articleView?id=platform.flow_build_logic_fault_email.htm&release=264.0.0&type=5)** As a best practice, we recommend configuring the fault connectors in your flow so that you always receive an email when a flow fails. In the email, include the current values of all your flow’s resources. The resource values can give you insight into why the flow failed. - **[Show a Custom Error Message in a Screen Flow](https://help.salesforce.com/s/articleView?id=platform.flow_build_logic_fault_usermsg.htm&release=264.0.0&type=5)** Add a fault path to a screen flow to show a helpful message when an element fails. - **[Other Examples of Error Handling in Flows](https://help.salesforce.com/s/articleView?id=platform.flow_build_logic_fault_examples.htm&release=264.0.0&type=5)** Examples of using fault connectors to handle flow errors include requesting corrections from the user and bypassing the error. #### See Also - [Flow Element Connectors](https://help.salesforce.com/s/articleView?id=platform.flow_ref_connectors.htm&release=264.0.0&type=5 "A connector determines the path that a flow takes at run time.") - [Flow Elements](https://help.salesforce.com/s/articleView?id=platform.flow_ref_elements.htm&release=264.0.0&type=5 "An element represents an action that the flow can run. Examples include reading or writing Salesforce data, displaying information and collecting data from flow users, runnning business logic, or manipulating data.") - [Move and Connect Elements to Change a Flow Route](https://help.salesforce.com/s/articleView?id=platform.flow_build_logic_route_add.htm&release=264.0.0&type=5 "Identify which elements the flow runs and in what order by connecting the elements on your canvas together. To change the run order, move elements and add or remove connectors.")