Examples of using fault connectors to handle flow errors include requesting corrections from the user and bypassing the error.
Required Editions
| View supported editions. |
Request Corrections from Users
Draw a fault connector to a Screen element, where users can verify the values that they entered, make corrections, and proceed.
Display the Error Message
If the flow is used only internally, such as at a call center, use the fault path to display the error message to the running user. In the same Screen element, ask the user to report the error to the IT department. To do so, draw the fault connector to a Screen element with this Display Text field.
Sorry, but you can’t read or update records at this time.
Please open a case with IT and include this error message:
{!$Flow.FaultMessage}Create a Case
When an error occurs, automatically create a case that includes
the error message and assign it to your IT department. Assign the created case’s number to a
Text variable ({!caseNumber}, for example). Then, in a
Screen, display this message to the running
user.
Sorry, but you can’t read or update records at this time.
We filed case {!caseNumber} for you.Ignore Errors
To bypass errors for a given element in your flow, draw the fault connector to the same element as the normal connector.