POWERSTUDIO365 BUILD GUIDE

Power Automate Error Handling Build Guide

The complete child flow blueprint: every TRY/CATCH stage, Configure Run After setting, and expression documented so you build it once and get it right.

pages

TRY/CATCH stages

test scenarios

Get the Build Guide

USD $15

Companion to the How to Stop Power Automate Errors From Going Unnoticed blog post

TRY

Get_item | ID: 999999999 ✗ NotFound

has failed · has timed out

CATCH

Filter_Failed_Actions

Send_Error_Notification →

Terminate (Failed)

⚠ Flow Failure Detected

FlowOrder_Routing

ScopeTRY

ActionGet_item

ErrorItemNotFound

is skipped → next TRY is skipped only

BEFORE THIS GUIDE

✗ Flows fail silently with no alert, no log record, and no indication of where the failure occurred
✗ Contact details and channel routing hardcoded in individual flows, requiring edits in multiple places when anything changes
✗ Notifications that arrive without the context needed to diagnose or act on the failure
✗ No structured way to verify error handling is working before a real business flow depends on it
✗ Hours spent on scope configuration, expression paths, and connector behavior differences with no single reference

WITH THIS GUIDE

✓ Every flow failure triggers a specific notification with the flow name, failed action, error message, and a direct link to the run
✓ A central configuration list routes notifications across every registered flow without touching individual flow logic
✓ Actionable Teams adaptive card alerts with the context needed to diagnose and resolve the failure quickly
✓ Five dedicated test scenarios that verify every failure path before the system connects to any real business flow
✓ Every scope configuration, expression, and schema decision documented so nothing is left to trial and error

What's included

Everything you need to build the full error handling system, from SharePoint list schemas to the adaptive card JSON.

Full child flow blueprint

All five TRY/CATCH stages built step by step. Every Configure Run After setting documented explicitly, including why is skipped and not is successful.

Adaptive card JSON

Paste-ready card payloads for both shared and private Teams channels, with the View Flow Run button and @mention expressions wired in.

SharePoint list schemas

Column-by-column specs for the Error Log and Notification Config lists, with correct data types, permissions, and filtered views included.

Config Values Helper flow

A production registration utility that looks up Teams channel and tag IDs automatically and writes the config record to SharePoint. No manual Graph API hunting required.

Key expressions reference

The coalesce error message expression, xrmWorkflowId vs Logic App name explained, Configure Run After quick reference, trigger body input indices for both flows.

Five test flows

Purpose-built instant flows that verify each failure scenario before connecting to a real business flow: shared channel, private channel, missing config, invalid channel ID, and invalid tag.

REAL TECHNICAL DEPTH

The details that actually matter

Different connectors store error messages at different paths. A single ?['error']?['message'] expression works for Power Automate expression failures but returns null for SharePoint, Dataverse, and most other connectors.

The guide documents the full coalesce() expression covering all three error structures plus a code fallback, so failures from any connector are captured.

/* Error message: works for any connector */
coalesce(
  first(body('Filter_Failed_Actions'))
    ?['error']?['message'],

  first(body('Filter_Failed_Actions'))
    ?['outputs']?['body']?['message'],

  first(body('Filter_Failed_Actions'))
    ?['outputs']?['body']?['error']
    ?['message'],

  first(body('Filter_Failed_Actions'))
    ?['code']  /* fallback: NotFound, BadRequest */
)
        

Resolves for: SharePoint · Dataverse · HTTP connectors · PA expression failures

Who this is for

Power Automate builders who read the blog post, understood the pattern, and want the scaffolding already done instead of rebuilding it scope by scope.

Builders shipping critical flows

Flows that process orders, trigger notifications, or integrate business systems where a silent failure costs more than the time to implement error handling properly.

Teams managing multiple flows

The centralized notification config means one setup covers every business-critical flow in your environment, not one CATCH scope per flow.

Practitioners tired of debugging

If you've lost time to Configure Run After settings, wrong GUIDs in View Run links, or adaptive cards rendering as HTML, this skips all of that.

Common questions

Do I need to read the blog post first?

The guide is designed as a companion to How to Stop Power Automate Errors From Going Unnoticed, so reading that post first gives context on why the architecture is designed the way it is. But the guide is self-contained and explains each decision as it's built.

What Power Automate license do I need?

A standard Microsoft 365 license that includes Power Automate is sufficient. The solution uses the SharePoint, Teams, and Outlook (Office 365) connectors, all standard connectors available on most plans. No premium connectors are required.

Does this work for any type of business flow?

Yes. The child notification flow is reusable. Register any business-critical flow in the Notification Config list and it automatically receives notifications when it fails. The guide includes a Config Values Helper flow that handles registration for you.

Is this for cloud flows only, or desktop flows too?

The guide covers cloud flows (automated, instant, and scheduled). The TRY/CATCH pattern and child notification flow architecture are specific to cloud flows. Desktop flows have different error handling mechanisms not covered here.

ONE-TIME PURCHASE

Build it once. Get it right.

The setup time on the first flow pays for this immediately. Every flow you register after that is a free benefit.

Get the Build Guide | $15

PDF · Instant download ·

Questions? help@powerstudio365.com