Standards

Power Platform Error Handling Standards

Shared expectations for canvas app errors, flow failures, retry behavior, logging, and support notifications.

Power Platform error handlingPower Automate try catchPower Apps IfError

Who this helps

Teams preparing apps and flows for real users and support owners.

What to standardize

Every production flow should have a failure path.
Every important save formula should use IfError or Errors.
User messages should explain what happened and what to do next.
Support logs should include enough context to reproduce the issue.

Examples

Flow error scope model

Handle failed automation without silent loss.

Formula / code

Scope - Try
  Create approval
  Update request status
Scope - Catch
  Log failed run
  Notify support owner
Scope - Finally
  Write processing timestamp

Expected result: Failures become visible and supportable instead of buried in run history.

Common mistakes

No run-after configuration
Emailing raw error JSON to users
Retrying non-idempotent updates blindly