Handle Power Automate Failures with Scopes and Run After: Series 5

Handle Power Automate Failures with Scopes and Run After: Series 5

Implement structured try/catch/finally handling and record actionable failures in Dataverse.

Implementation approach

Use three scopes: Try, Catch, and Finally. Place business actions in Try. Configure Catch to run after Try has failed, timed out, or been skipped. In Catch, capture workflow name, run identifier, record ID, failed action, and a safe error summary. Update a custom Automation Log row or notify support. Configure Finally to run after the Try/Catch paths as appropriate. Do not expose raw connector responses or secrets to end users. Use retry policies for transient failures, not for invalid data or permission errors.

Recommended validation

  • Build the flow inside a solution and use connection references.
  • Test with real Dataverse security roles and least-privilege connections.
  • Handle retries, duplicate triggers, timeouts, and connector failures.
  • Keep business status and audit data in Dataverse.
  • Verify the complete process in a non-production environment before deployment.