Skip to content
JTS

Loading advanced system settings…

Your Power Automate flows are failing silently right now. Use TRY/CATCH to solve it

Knowledge article · 10 May 2026

Source
LinkedIn
Status
Published

Content

How to replicate try/catch in Power Automate with two Scope actions and "Configure run after", and why it makes the difference in production.

Summary of the article published on LinkedIn. “View original” opens the full text with screenshots.

The idea

Power Automate has no native try/catch syntax, but you can replicate it with two Scope actions:

  • Scope TRY: all your real logic (HTTP calls, updates, transforms).
  • Scope CATCH: runs only when TRY fails. Log the error, send an alert, notify someone.

How to configure it

  1. Create the TRY scope with all your flow logic.
  2. Create the CATCH scope with your error handling.
  3. In the CATCH settings, change Configure run after so it runs when TRY fails or times out.

The result() expression captures exactly which action failed and why.

Why bother

  • No more silent failures: every error triggers a log, an email or a Teams message.
  • Faster debugging, without digging through 30 steps of run history.
  • You decide what happens next: retry, notify, roll back or skip.
  • It also covers timeouts from slow or unavailable services.

Two scopes, one expression, zero silent failures.

General

Published
10 May 2026
Source
LinkedIn