CRT-101 · Question #53
Cloud Kicks users are seeing error messages when they use one of their screen flows. The error messages are confusing but could be resolved if the users entered more information on the account…
The correct answer is C. use a fault connector and display a screen with text explaining what went wrong and how to. In Flow Builder, a Fault Connector can be added to any element that might encounter a runtime error (such as a Create/Update element). When an error occurs, the flow follows the fault path to a Screen element that displays a friendly, informative message telling the user what…
Question
Cloud Kicks users are seeing error messages when they use one of their screen flows. The error messages are confusing but could be resolved if the users entered more information on the account before starting the flow. How should the administrator address this issues?
Options
- ARemove validation rules so that the users are able to process without complete records.
- BCreate a permission set to allow users to bypass the error.
- Cuse a fault connector and display a screen with text explaining what went wrong and how to
- DUncheck the end user Flow Errors box in setup.
How the community answered
(41 responses)- A2% (1)
- B10% (4)
- C80% (33)
- D7% (3)
Explanation
In Flow Builder, a Fault Connector can be added to any element that might encounter a runtime error (such as a Create/Update element). When an error occurs, the flow follows the fault path to a Screen element that displays a friendly, informative message telling the user what went wrong and what information they need to provide before restarting. This is the proper way to handle flow errors gracefully. Removing validation rules (A) compromises data integrity. Creating a permission set (B) cannot bypass runtime flow errors. The 'End User Flow Errors' checkbox option (D) does not exist as described in Salesforce setup.
Topics
Community Discussion
No community discussion yet for this question.