Clayton

Flows that interact with the Salesforce database can fail. As a best practice, all fault paths should cover by error handlers.

All steps that interact with DB ("recordUpdates", "recordCreates", "recordDeletes", "recordLookups")

All steps that invoke Apex classes ("actionCalls")

- All steps that interact with DB ("recordUpdates", "recordCreates", "recordDeletes", "recordLookups")
- All steps that invoke Apex classes ("actionCalls")

<a href="https://help.salesforce.com/s/articleView?id=sf.flow_prep_bestpractices.htm&amp;type=5" rel="nofollow noopener noreferrer" target="_blank">Flow Best Practices</a>

<a href="https://help.salesforce.com/s/articleView?id=sf.flow_build_logic_fault.htm&amp;type=5" rel="nofollow noopener noreferrer" target="_blank">Customize What Happens When a Flow Fails</a>

<a href="https://help.salesforce.com/s/articleView?id=sf.flow_build_logic_fault_email.htm&amp;type=5" rel="nofollow noopener noreferrer" target="_blank">Configure Every Fault Path to Send You an Email (Best Practice)</a>

- <a href="https://help.salesforce.com/s/articleView?id=sf.flow_prep_bestpractices.htm&amp;type=5" rel="nofollow noopener noreferrer" target="_blank">Flow Best Practices</a>
- <a href="https://help.salesforce.com/s/articleView?id=sf.flow_build_logic_fault.htm&amp;type=5" rel="nofollow noopener noreferrer" target="_blank">Customize What Happens When a Flow Fails</a>
- <a href="https://help.salesforce.com/s/articleView?id=sf.flow_build_logic_fault_email.htm&amp;type=5" rel="nofollow noopener noreferrer" target="_blank">Configure Every Fault Path to Send You an Email (Best Practice)</a>

Detect Flows that don't use Fault Paths on every step

Missing fault path in Flows

Home

Find answers and get help from Intercom Support and Community Experts

Link, Press control-option-right-arrow to exit

Empty Help Center

Uh oh. That page doesn’t exist.

Disappointed

Neutral

Smiley

Thinking...

Searching through sources...

Analyzing...

Title

Track the progress of all tickets related to your company.

Tickets portal.

{assigneeName} needs more information from you

Missing fault path in Flows

Scope

Resources