Give every Power Automate flow an error trap, not just a happy path

Most Power Automate flows I audit have a happy path and nothing else. The first time an approver's mailbox is full, or a SharePoint list column gets renamed, the flow fails silently - no error to the user, no alert to you, just a run that quietly didn't do the thing.

The fix is one configuration change, every time:

• Select the action that can fail (an approval, an HTTP call, a create-item step).
• Set "Configure run after" to include the failed/skipped/timed-out states, not just succeeded.
• On that branch, post to a Teams channel or send yourself an email naming the flow, the run, and what failed.
• Add a Scope block around the risky actions if there's more than one, so one error handler covers the whole group instead of wiring up each action individually.

Checklist before you call any flow "done":

1. Does it alert you, not just fail quietly?
2. Does the alert name the record it was working on, not just "a run failed"?
3. Have you actually triggered the failure case once, on purpose, to watch it work?

If a flow touches access, money, or a compliance deadline and you haven't done step 3, you don't know it works - you know the happy path works.