--- schema_version: "1" id: 9773a062de49e50a58d341a7b5c3551ae0fa0d32e676729cab1bc97fe30880a4 title: Default Flow Error Handling 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_default.md canonical_url: https://help.salesforce.com/s/articleView?id=platform.flow_build_logic_fault_default.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: b0b4728e84c5619b44f3336660b7ff4f9344d9d082cfb611a05eb3cefbd6ba91 description: 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. products: - Flow Builder - Salesforce Platform release: "264" --- # Default Flow Error Handling 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. ### Required Editions
View supported editions.
## How Flow Type Affects Error Handling The behavior of a fault path depends on the flow type and the elements in the path. Some elements perform Data Manipulation Language (DML) operations, which create, update, or delete Salesforce records. DML elements include Create Records, Update Records, and Delete Records. Some core actions and Apex actions can also perform DML operations. This table describes fault paths that contain a DML element. An empty fault path has the same behavior as a fault path with no elements. | Flow Type | No Fault Path or Empty Fault Path | Fault Path | | --- | --- | --- | | Record-triggered flow | Salesforce blocks the triggering change and rolls back the transaction. If a user changes a record on a record page, Salesforce shows an unhandled-fault message. If a validation rule causes the error, Salesforce shows that rule’s error message instead. | Salesforce doesn't block the triggering change. The flow runs the fault path, and Salesforce doesn’t roll back the transaction. Salesforce shows an error message only if the fault path includes an Error element. | | Screen flow | Salesforce shows an unhandled-fault message and rolls back the transaction. | The flow runs the fault path. If the path doesn’t include a Screen element, Salesforce shows a completion message. Salesforce rolls back the transaction only if the path includes a Roll Back Records element. | | Autolaunched flow | Salesforce shows an unhandled-fault message and rolls back the transaction. | The flow runs the fault path, shows a completion message, and doesn’t roll back the transaction. | ## What Happens Without a Fault Path When an element has no fault path or an empty fault path and it fails, Salesforce displays this error message and creates a failed interview. ``` An unhandled fault has occurred in this flow An unhandled fault has occurred while processing the flow. Please contact your system administrator for more information. ``` The running user can’t proceed with the flow or return to a previous part of the flow. The configured recipient receives a fault email. For information about choosing error email recipients, 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."). The email details the element that failed, the error message from that element, and which elements ran during the failed interview. Here’s an example error message. ``` An error occurred at element Delete_1. DELETE --- There is nothing in Salesforce matching your delete criteria. ``` To view the debug details directly in Flow Builder, click **Flow Error: Click here to debug the error in Flow Builder** in the fault email. This link appears only for certain flow types. For screen flows, Salesforce publishes a Flow Execution Error Event platform event message. #### See Also - [Customize What Happens When a Flow Fails](https://help.salesforce.com/s/articleView?id=platform.flow_build_logic_fault.htm&release=264.0.0&type=5 "Learn how fault paths customize what happens when a flow fails. Choose how to notify admins, guide users, and take a follow-up action.") - [Troubleshooting Flow Run Time Errors](https://help.salesforce.com/s/articleView?id=platform.flow_troubleshoot_email.htm&release=264.0.0&type=5 "Learn how to troubleshoot and resolve flow errors and unexpected behavior in your flows that occur after activation. Interpret error emails, and use best practices to identify and resolve issues quickly.") - [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.") - [Send Alerts When a Screen Flow Fails](https://help.salesforce.com/s/articleView?id=platform.process_troubleshoot_error_event.htm&release=264.0.0&type=5 "To save time troubleshooting screen flows that fail, subscribe to the Flow Execution Error Event platform event. When a flow interview fails, Salesforce publishes a platform event message. In Process Builder, you can subscribe to the platform event and perform actions, such as posting to Chatter or sending custom notifications.")