Fault paths for flow error handling
Key Takeaway
A failed flow element with no fault path stops the flow. With a fault path, the flow follows that path instead, and the user doesn't see the unhandled fault message.
When a flow element that interacts with the Salesforce database fails, the default result is a generic error message for the user. A fault path is a secondary path on the Flow Builder canvas that runs only when its source element fails. It lets you decide what happens next instead of accepting the default error.
What happens when a flow element fails
Flow elements that interact with the Salesforce database can fail, such as Update Records or a Submit for Approval core action. A failure like this is called a fault. Common causes of faults include:
- Creating a record with a field the running user can't access
- Editing a record the user can't access
- Creating a record without setting a required field
- Using a record ID with the wrong number of characters
- Sending email to an invalid address
- Doing something a validation rule blocks
If the element has no fault path, the flow stops by default. The running user sees the generic unhandled fault 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.
An unhandled fault stops the flow in every flow type, but it looks different depending on the flow type. In a record-triggered flow, the user sees a "We hit a snag" error saying the record can't be saved because the automation failed.