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.
To open, edit, create, activate or
deactivate a flow using all flow types, elements, and features available in Flow
Builder, including Einstein and Agentforce for Flow:
Manage Flow
Note You don't need to be an admin to have the Manage Flow permission.
Ask your admin to add it to your profile or permission set.
Create a text template that contains a friendlier error message.
<p><b>Something went wrong with this flow.</b></p>
<p>Your admin has received an email about this error.</p>
Add a Screen element. In a Display Text screen component, reference the text template.
For every element that can fail, draw a fault connector to the Screen element.
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.
