Monitoring Power Automate Flows

Monitoring flows is always a challenging task. Once the environment grows the solution also grows along with flows too. There are few ways we can able to monitor flows.

Option 1 :

From the Admin Centre we can able to get Analytics on how the flow are the progressing. There are some useful insights available like Runs, Usage, Created, Errors, Shared. as below.

Analytics -> Power Automate -> Errors is our interest area which gives information on the common error messages. It also gives a table that shows which flow failed how many times and the last occurred date. It can be exported as a raw data in excel format. Drawback about this is it only gives us the flow id and not the name of the flow. But still these are pretty useful information’s.

Option 2 :

The next method is navigate to the individual flow and press Analytics.

The Analytics will be shown something like below. Good thing about this data is that it will tell even deeper information on the which steps got more error and what is the error message it is getting. Practicality is the issue here, we can’t simply go in to each and individual flows to monitor every day.

Option 3 :

Building a custom monitoring solution. This can be achieved using multiple way with custom approach sky is the limit. We can do whatever way we want to get notified. Some of the practical options are

• Teams Channel
  • Pros
    • Notification is seamless.
    • Onboarding/offboarding user is centralised in Active Directory. Channel membership needs to be catered.
    • Actioning and assignment for the task is easy can tag people in the comments and easy peasy.
  • Cons
    • Not much of reporting or any insights we can’t get if needed for any review purposes.
• Email to an Admin Group
  • Pros
    • Notification is seamless.
    • Onboarding/offboarding user is centralised in Active Directory.
    • Actioning and assignment for the task is bit tricky with emails.
  • Cons
    • Not much of reporting or any insights we can’t get if needed for any review purposes.
• Create a custom Dataverse table and add rows on every errors.
  • Pros
    • Onboarding/offboarding user is centralised in Active Directory.
    • The error details can be capture in a more granular way which helps reporting.
    • Once capture in that table, notifying via Team or Email is also even possible.
  • Cons
    • Reporting and extracting of information is more effectively. Can even create fancy dashboard for visual treat 🙂
    • Actioning and assignment for the task is bit tricky with records sitting in Dataverse though.

“The sky is not the limit. Your imagination is.”