Flow fault paths and error notifications
Key Takeaway
A fault path turns off the automatic rollback. Changes from earlier elements stay saved, and in a record-triggered flow the triggering change saves too. To roll back on a fault path, use Roll Back Records in screen flows or Custom Error in record-triggered flows.
A flow can fail when one of its elements hits an error, for example while creating or updating a record. By default, the flow stops and shows the user a vague error. Salesforce also emails an admin. With a fault path, you decide what the flow does instead: show a clearer message, email someone the details, or roll back changes.
What happens when a flow element fails
Any flow element that works with the Salesforce database can fail. Examples are an Update Records element and a Submit for Approval core action.
When an element fails and no fault path handles the error, the result is an unhandled fault. By default, an unhandled fault stops the flow and shows the running user this message: "An unhandled fault has occurred in this flow." The user can't continue or go back to an earlier part of the flow, so they must start over.
Common causes of unhandled faults include:
- Creating a record with a field the running user can't access
- Editing a record the running user can't access
- Missing a required field
- Using a record ID with the wrong number of characters
- Sending email to an invalid address
- Hitting a validation rule