You are here:
Test a Flow for Error Handling
Configure negative assertions to verify that a flow handles errors gracefully when you use automated testing.
You are here:
Configure negative assertions to verify that a flow handles errors gracefully when you use automated testing.
| View supported editions. |
| User Permissions Needed | |
|---|---|
| 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 |
Configure negative assertions for Create Records, Update Records, Delete Records, and Action elements in any flow that uses automated testing, including autolaunched, record-triggered, and Data Cloud-triggered flows.
For more information about configuring assertions when you set up a test scenario in test mode, see Set Up and Run a Test Scenario (Beta).
Consider a flow that processes customer data. You can create a test scenario to make sure that the flow handles invalid input, such as a missing required field.

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 are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security 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 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.