If your flow contains an element that interacts with the Salesforce
database—such as an Update Records element or a Submit for Approval core
action—it can fail. Modify the default behavior by adding fault paths to all elements
that can fail.
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.
Select Flow and Process Error Email Recipients 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 was executed 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 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.
Customize the Error Message for Running Flow Users (Best Practice) As a best practice, we recommend displaying a better message to your user than “An unhandled fault has occurred in this flow”. Display a new message only if the distribution method you’re using supports flows that contain screens. In other words, don’t do it if your flow is distributed through a process.
Other Examples of Error Handling in Flows Examples of using fault connectors to handle flow errors include requesting corrections from the user and bypassing the error.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.
