how to use result('Scope_Try') in a Compose to extract the failed action name from inside a catch

By Sai Kiran Pandrala · Last verified: 2026-05-31 · Source: community forums (r/nocode, r/automation, r/GoogleAppsScript, r/PowerAutomate, r/n8n, r/make, r/ClaudeAI), vendor status pages and changelogs, vendor help centers, in-product help

Running into how to use result('Scope_Try') in a Compose to extract the failed action name from inside a catch on Power Automate Error Handling, Run After, Scope Try-Catch & Retry Policies, 2026 is one of the more common stalls I see when I am deep in a scenario or a script and the platform suddenly refuses to cooperate. My standard pattern for this is to capture the run history first, then walk the fix below - here is what actually moves the needle when the vendor docs are too generic and you do not have time to file a support ticket.

What how to use result('scope_try') in a compose to extract the failed action name from inside a catch actually involves on Power Automate Error Handling, Run After, Scope Try-Catch & Retry Policies, 2026

On Power Automate Error Handling, Run After, Scope Try-Catch & Retry Policies, 2026 the first three tools that earn their keep are Flow Checker validation pane, Charles Proxy or Fiddler to capture outbound action traffic, Cloud flow Monitor view (preview) for cross-run failure trends. Each of these surfaces a different layer of the failure - keep at least the first one in your personal notes so the next time this happens you do not start cold.

For verification on Power Automate Error Handling, Run After, Scope Try-Catch & Retry Policies, 2026, the methods that survive contact with a real Monday-morning workload are test the failure path by temporarily breaking the endpoint URL and confirming catch path executes and run history of the catch Scope must show Status=Succeeded while the Try Scope shows Status=Failed. Anything less than that and you are shipping on vibes.

Authoritative sources for Power Automate Error Handling, Run After, Scope Try-Catch & Retry Policies, 2026 that I cross-reference before committing to a fix: learn.microsoft.com/en-us/azure/logic-apps/logic-apps-exception-handling, github.com/MicrosoftDocs/power-automate-docs, learn.microsoft.com/en-us/power-automate/guidance/coding-guidelines/error-handling. Marketing blog posts and Medium writeups are signal, not ground truth.

The rest of this page is the structured fix path. Start with diagnose, then remediation, then the automation options so you do not have to do this by hand the next time it surfaces. Verify and safety sections at the end are the discipline that keeps the fix from regressing the next time you open the platform.

Signal review

Start by capturing the exact failure signal in writing before you change a single thing on your Power Automate Error Handling, Run After, Scope Try-Catch & Retry Policies, 2026 setup. In the browser that is the failing request in DevTools Network tab (right-click, Copy as cURL) plus the JS console error. In the platform UI that is the error toast text, the timestamp, and the scenario or workspace id from the URL. On the Power Automate Error Handling, Run After, Scope Try-Catch & Retry Policies, 2026 status page capture the incident id and timestamp. Screenshot it. Do not paraphrase. Most Power Automate Error Handling, Run After, Scope Try-Catch & Retry Policies, 2026 support workflows will not even route the ticket without the workspace id or correlation id - the support rep pastes it straight into the internal trace tool and the first response is "we see your request, here is what the backend logged."

Second pass: open the Power Automate Error Handling, Run After, Scope Try-Catch & Retry Policies, 2026 workspace admin or settings panel and look at the audit log or activity feed for the failing window. Most modern automation platforms surface an audit trail (the platform's execution history, the connector run log, the integration activity feed). The audit log tells you whether the failure was your action, a teammate changing a connected account in the same minute, or a platform-side rollout. Many "permission denied" or "connection not found" reports trace to a credential-level change pushed in the same admin panel in the previous hour - the audit trail makes that obvious without guesswork.

Sixth: pin down the latency and reliability envelope on the Power Automate Error Handling, Run After, Scope Try-Catch & Retry Policies, 2026 session under real working conditions. Run a long-duration sanity test by executing the failing scenario 10 times over 15 minutes, logging the timestamp and the result (success / error code / which step failed) per attempt to a notes file. Watch for the breakpoint where the success rate dips below 80 percent - that is your real signal that something is wrong, not the one-off failure that prompted the investigation. If you are on a marginal network (cafe wifi, mobile hotspot, hotel network), run the same test on a wired or known-good connection before assuming the platform is the problem. Capture the breakpoint in your personal notes next to the platform version, the account, and the workspace id - the next time this happens to a teammate, the notes are gold.

Field notes from real Power Automate Error Handling, Run After, Scope Try-Catch & Retry Policies, 2026 incidents

I keep Postman to reproduce the underlying connector REST call docked on a second screen whenever I am building inside Power Automate Error Handling; one glance tells me whether the run actually fired or silently skipped. Before I mark an Power Automate Error Handling ticket resolved I always run `in Monitor view filter Status=Failed and confirm the failure trends to your expected error class` once more and screenshot the output, that habit has caught at least three silent regressions for me.

After any change to an Power Automate Error Handling automation I run `run history of the catch Scope must show Status=Succeeded while the Try Scope shows Status=Failed` to confirm the run actually held, two seconds, one call, zero ambiguity. Vendor docs at learn.microsoft.com/en-us/power-automate/limits-and-config are a starting point for Microsoft questions, not the truth. The community threads are where the real edge cases land.

Tools I actually reach for

For most Power Automate Error Handling, Run After, Scope Try-Catch & Retry Policies, 2026 stalls I start with Cloud flow Monitor view (preview) for cross-run failure trends, fall back to Browser DevTools Network tab on flow.microsoft.com/manage/runs, Flow Checker validation pane, Power Platform admin center > Analytics > Cloud flows runs when Cloud flow Monitor view (preview) for cross-run failure trends cannot surface the answer, and keep JSON expression evaluator inside the Compose action handy for the cases where neither answers. That ordering is not academic - it matches the layers of the failure as they tend to surface, so the cheapest signal lands first and the heavier tooling only comes out when the simpler answer does not hold up. My muscle-memory shortcut for this is to run the first tool while the failing screen is still open, not after I have already restarted the platform.

Verification I run before I call it fixed

Before I mark a Power Automate Error Handling, Run After, Scope Try-Catch & Retry Policies, 2026 stall resolved, the verification loop below is what I actually run. Each step proves a different layer is green, and the order matters - the cheaper checks gate the more expensive ones.

right-click target action > Configure run after > tick has failed, is skipped, has timed out, save

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

in Monitor view filter Status=Failed and confirm the failure trends to your expected error class

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

run history of the catch Scope must show Status=Succeeded while the Try Scope shows Status=Failed

Only when every line above runs clean do I close the loop and update my notes with the timestamps.

Where I check first when the docs disagree

When two sources contradict each other on a Power Automate Error Handling, Run After, Scope Try-Catch & Retry Policies, 2026 detail, the disambiguation order I lean on is stable. I usually check learn.microsoft.com/en-us/power-automate/limits-and-config for the ground-truth view on this part of Power Automate Error Handling, Run After, Scope Try-Catch & Retry Policies, 2026. I usually check learn.microsoft.com/en-us/azure/logic-apps/logic-apps-exception-handling for the ground-truth view on this part of Power Automate Error Handling, Run After, Scope Try-Catch & Retry Policies, 2026. I usually check github.com/MicrosoftDocs/power-automate-docs for the ground-truth view on this part of Power Automate Error Handling, Run After, Scope Try-Catch & Retry Policies, 2026. Marketing blog posts and Medium writeups are signal, not ground truth, and I treat them as such until the references above either confirm or contradict the claim.

Solution-focused remediation path

When the Power Automate Error Handling, Run After, Scope Try-Catch & Retry Policies, 2026 platform returns intermittent errors, run delays, or "something went wrong" under normal load, suspect the vendor before blaming your setup. Subscribe to the Power Automate Error Handling, Run After, Scope Try-Catch & Retry Policies, 2026 status page RSS or webhook so an open incident lights up your inbox or Slack automatically. Cross-check the vendor Trust Center for any planned maintenance window covering your region. Listen to the vendor X/Twitter status handle - many incidents land there 15 to 30 minutes before the formal status page update. Decision point: if the status page is green but multiple teammates in the same region are seeing the same toast, fail over to the web app (if the desktop client is broken) or to a different device (if the web app is broken) and file a support ticket with the failing screenshot, the workspace id, and the timestamp window; major vendors all accept the workspace id as the primary trace key. Screenshot the failing run with the network indicator and the platform version visible before the failover - that screenshot is what the support team asks for first on any latency or error report.

For any Power Automate Error Handling, Run After, Scope Try-Catch & Retry Policies, 2026 failure that smells like auth or permission, walk the principle of least surprise chain in order. Confirm which account you are actually signed into (top-right avatar on web, account menu on desktop, profile tab on mobile) and confirm it matches the email the connector is bound to. Many "my scenario stopped firing" reports trace to the connector being bound to your personal account while you are signed into your work workspace identity on the same browser profile. Sign out of every account, sign back in with only the canonical work account, and retry. Clear the OAuth grant from the Power Automate Error Handling, Run After, Scope Try-Catch & Retry Policies, 2026 connected-apps page if you suspect a stale third-party token (the platform's connector settings, the upstream provider's "third-party apps" page). Decision point: if the account is correct, the connector is bound to that account, and the action still fails with a permission error, ask the workspace owner to re-grant the scope explicitly and to check their workspace-level connector policy for a new restriction.

If the Power Automate Error Handling, Run After, Scope Try-Catch & Retry Policies, 2026 platform is slow, stale, or serving cached errors, work the cache and CDN stack in order. Sign out of the desktop app or browser session, quit it fully (Cmd+Q on macOS, right-click the system tray icon -> Quit on Windows - not just the close button), reopen, sign back in. Clear the local cache (most platforms expose this under Help -> Clear cache, or Settings -> Advanced -> Reset cache). Hard-refresh the web app with Ctrl+Shift+R (or Cmd+Shift+R on macOS) to bypass the local browser cache. Always capture timing before the cache clear to baseline: time how long the failing run takes three times, write it down, then repeat after the cache clear so the delta is provable in your notes. Decision point: managed-device issues go through your IT admin for a tenant-wide config push; personal-device issues go through the in-product Help + Diagnostics flow before you escalate to support.

Automate this fix so you do not do it twice

Monitor + alert via Power Automate Error Handling, Run After, Scope Try-Catch & Retry Policies, 2026 admin reports, audit logs, and personal dashboard ingestion

For the Power Automate Error Handling, Run After, Scope Try-Catch & Retry Policies, 2026, the most useful long-running telemetry is the admin reports + audit logs shipped to a personal dashboard (Google Sheets daily import, Airtable scheduled sync, Notion database via the API, Grafana with a CSV source) and graphed on a single view. Pair that with synthetic monitoring (a small script that triggers the failing scenario or runs the failing action every 5 minutes from at least two devices) so a regional incident lights up before teammates report it. Subscribe the personal inbox or a private Slack channel to the Power Automate Error Handling, Run After, Scope Try-Catch & Retry Policies, 2026 status page (Atom/RSS or Statuspage webhook) plus the vendor X/Twitter status handle so an open incident self-correlates with the synthetic failures.

# Tiny synthetic monitor - hit the Power Automate Error Handling, Run After, Scope Try-Catch & Retry Policies, 2026 health endpoint every 5 minutes
while true; do curl -s -o /dev/null -w "%{http_code} %{time_total} $(date -Iseconds)\n" \ -H "Authorization: Bearer $TOKEN" \ https://api.example.com/v1/me \ >> ~/logs/power-synth.log sleep 300
done

Codify the platform version pin and rollback as a single notes entry

Once a stable platform version is identified for the Power Automate Error Handling, Run After, Scope Try-Catch & Retry Policies, 2026, write the version string, the build hash, and the workspace policy state to a personal notes entry with the date in the title. Reproducible rollback is then a single download-and-install plus a sign-in. Pin the workspace policy state explicitly so a vendor-side default change does not silently shift behavior under you. Stage the notes entry next to a checklist that lists the failing screenshot, the Power Automate Error Handling, Run After, Scope Try-Catch & Retry Policies, 2026 incident id (if any), and the support case number; the second time the workflow breaks at 9 a.m. you do not want to be rediscovering which platform build was actually green.

# Personal notes template (power)
Date: 2026-05-31
Platform: power
Working build: 2.45.1 (Build hash: a1b2c3d)
Account: work@example.com
Workspace: ws-prod-power
Failing screenshot: ~/notes/power-2026-05-31.png
Support case: SUPP-power-12345
Rollback path: download installer from vendor releases page, sign out, reinstall, sign back in

Scrape Power Automate Error Handling, Run After, Scope Try-Catch & Retry Policies, 2026 workspace audit log + integration log via scheduled job

For the Power Automate Error Handling, Run After, Scope Try-Catch & Retry Policies, 2026, workflow faults usually surface as failed run executions, audit-log denials, or quota nags before a full hang. A weekly scheduled job that exports the last 7 days of these events to CSV gives you a paper trail to correlate with platform updates, policy changes, and vendor incidents without staring at the settings panel live. Register the task via cron (Linux / macOS), Windows Task Scheduler (schtasks /create /XML), or a GitHub Actions schedule, then write the CSV to Dropbox / OneDrive / Google Drive for retention. Subscribe a simple dashboard (Google Sheets with a daily import, Airtable scheduled sync, Notion database via the API) to the same bucket so audit events from every Power Automate Error Handling, Run After, Scope Try-Catch & Retry Policies, 2026 workspace converge on a single view without per-workspace clicking.

# Export the platform audit log via the API (Enterprise plan)
curl -X POST https://api.example.com/v1/audit_logs \ -H "Authorization: Bearer $PLATFORM_TOKEN" \ -H "Accept: application/json" \ -d '{"start_date":"2026-05-24","end_date":"2026-05-31"}' \ -o power-audit-log.json
# Export the run history for the last 7 days
curl -G https://api.example.com/v1/runs \ -H "Authorization: Bearer $PLATFORM_TOKEN" \ --data-urlencode "oldest=$(date -d '7 days ago' +%s)" \ -o power-runs.json

Things that bite

Platform auto-updates during an active failure are the textbook way to break a Power Automate Error Handling, Run After, Scope Try-Catch & Retry Policies, 2026 workflow further, and the trap catches experienced builders because the release notes look like they describe exactly the bug at hand. Never accept a major platform version bump while you are in the middle of debugging, never push a beta build unless the release notes tie it to a specific advisory for your symptom, and never roll forward when a rollback is available. Skipping a required workspace-policy migration leaves a known regression path open even after the immediate fix, so check the deprecation timeline on the Power Automate Error Handling, Run After, Scope Try-Catch & Retry Policies, 2026 changelog before deciding to wait.

The other half is trusting the vendor status page verdict by itself. Vendor status pages can miss regional incidents that only hit one POP, the Trust Center will not flag a connector degradation, and the activity feed entries can lag several minutes behind the actual failure. Cross-reference the vendor X/Twitter status handle, Downdetector, the failing screenshot timestamps, and the on-screen symptom narrative before committing to a destructive remediation on Power Automate Error Handling, Run After, Scope Try-Catch & Retry Policies, 2026.

Repair sequence

• Reproduce the original failing run against Power Automate Error Handling, Run After, Scope Try-Catch & Retry Policies, 2026 on the same device AND a second device with the same account. If the failing toast or error code still surfaces on any device, you have not fixed it.
• Watch for 24 to 48 hours via the Power Automate Error Handling, Run After, Scope Try-Catch & Retry Policies, 2026 workspace audit log + the integration history + your personal notes. Cached error states and CDN caches mask slow-burn drift and intermittent regional issues.
• Smoke-test under realistic load: replay the workflow against a test workspace for at least 30 minutes at your normal working pace, log success / error and the timestamp per attempt to a notes file.
• Capture the new state in a personal notes entry so the next time this happens you do not rediscover it. Note platform version + workspace policy + connected-apps list + failing screenshot + verbatim error string + fix applied. Push to a shared team wiki if your team uses one.
• If the fix involved an API token rotation or a workspace policy change, commit the new token to your password manager and screenshot the workspace settings for archival.

Safety, rollback, blast radius

• Test in a Power Automate Error Handling, Run After, Scope Try-Catch & Retry Policies, 2026 test workspace or on a duplicate scenario first before any change that touches the real workspace. Snapshot the platform version, the workspace settings, the connected-apps list, and the sharing policy before changing anything.
• Apply the principle of least surprise when granting share access or connected-app permissions. Review the share list against the people who actually need access - extra shares are extra blast radius.
• Use idempotent runs where the Power Automate Error Handling, Run After, Scope Try-Catch & Retry Policies, 2026 API supports it (the platform's run id de-dupe, external id keys on destination records) so a retried run does not create duplicate records.
• Know your rollback path. Platform version rollback is a one-line download-and-install; an API token rotation is reversible if you kept the old token in the password manager during cutover; a workspace policy change is reversible only if you saved the previous policy in a screenshot.
• For team-wide or workspace-wide changes, line up a maintenance window with team notification before pushing through the admin console.

FAQ

Related fixes

Related guides worth a look while you sort this one out:

• how to differentiate a skipped action from a failed action when computing Scope final status
• how to use a Terminate action with status Failed and a custom error code to fail the parent flow
• how to wrap a sensitive action in a Scope and email administrators with the result() catch payload
• how to use Scope blocks in Power Automate to group try and catch for connector error handling
• how to use HTTP with Azure AD action with managed identity from a Power Automate Premium plan
• how to use the filter array action with an OData-style expression in Power Automate without nesting Apply to each