Power Automate Intermediate Lesson 5: Error Handling With Scopes and Run After

📘 Power Automate Intermediate Course · Lesson 5 of 8

A flow that fails silently is worse than no flow. Wrap the work and react to failure.

1. Add a Scope named Try and put the main actions inside.
2. Add a second Scope Catch after it > … > Configure run after: tick has failed and has timed out, untick is successful.
3. In Catch: post a Teams message or email with the flow name, the error and a link to the run:
   concat('https://make.powerautomate.com/environments/', workflow()?['tags']?['environmentName'], '/flows/', workflow()?['name'], '/runs/', workflow()?['run']?['name'])
4. End Catch with Terminate (Failed) so the run history shows failure.

Retries

Most connector actions retry automatically on temporary errors (Settings > Retry Policy). Increase it for flaky APIs; set None for actions that must not repeat (sending payments, posting messages).

Practice

Add Try/Catch to the approval flow from lesson 3 and force a failure (rename the Excel table) to test the alert. Build it in your own Microsoft 365 account at make.powerautomate.com, test it with the practice file, and check the run history.