04 · Fault paths and error handling

Every element that touches the database can fail. Decide on purpose what happens when it does.

The fault connector nobody drags

Every Create, Update, Delete and Action element has a fault path waiting. Drag it to a subflow that logs the error and notifies someone — once, centrally, for every flow you own.

What to tell the user

'An unhandled fault has occurred' is a resignation letter. A caught fault can say: your record was saved, the follow-up email was not, and an admin has been notified.

Practice in your org

• Open your Developer Edition org and follow along step by step
• Change one thing at a time and note what happens
• When something breaks, read the error before searching for it