What it requires. All DML elements (Create Records, Update Records, Delete Records) and Apex Action elements must have a fault path connector configured.
Why it matters. Without fault paths, any runtime error – including governor limit exceptions, permission errors, or database failures – produces a generic unhandled exception visible to the end user and sends no notification to administrators. Fault paths allow controlled error handling, user-friendly messages, and error logging.
How to fix it. Add a fault path to every DML and Apex Action element. At minimum, route to a screen element with a user-friendly message for screen flows, or an email alert for autolaunched flows. Consider a shared error-handling subflow for consistency.
Source. Salesforce Help: Customize What Happens When a Flow Fails (fault paths)
Is this rule worth checking?
Votes and comments are published here. We read them, and we publish what we change with the reasoning — a vote does not move a rule on its own.