Effectively Find and Investigate Failed MS Flow Runs

Introduction

We are huge fans of MS Flow and the transformative effects it can have on business processes.

One of the scenarios we’ve recently encountered involved an automation that was run hundreds of times over the course of roughly an hour.

In this case, our Flow ran over 1500 times and there were a hand full of failed runs. We wanted to isolate the errors, but there were a lot of runs to check through.

Quick Tips on Finding Flow Run Failures

If you’re trying to work through finding a few failures within a run history filled with many successful runs, here are a couple of quick tips! So you can avoid doing this:

You don’t need to do the long scroll!

You don’t need to do the long scroll!

Tip 1: Find What Failed

You can use the analytics page for a quick look at what is happening with your Flow. It provides you with a filterable view (by time span) of analytics about your Flow. There is also a specific Errors page in the analytics that reveals more information about the errors in your Flow. Here is a link to a post on the the Flow blog - all about the release of this great feature.

Note: The Flow Analytics page requires a Plan 2 license

Flow Details Page > Analyitics

Flow Details Page > Analyitics

Analytics for your runs history!

Analytics for your runs history!


Tip 2: See the Run History for a Specific Flow

You don’t need the analytics page to find the errors in your Flow. You can also use the See All link found in the Run History section of your Flow’s details page.

The Run History section is the first place to get started. For anyone new, you can go to your Flow’s details page and look for the Run History section.

You can click on See all > to view a longer history of your Flow runs.

Flow Run History - See how things go with your Flow

Flow Run History - See how things go with your Flow

Tip 3: Filter the Run History

Below is a view of the Run History screen (shown on left) . It provides a longer (and scrollable) history of the Flow’s runs. However, you might find yourself working through a lot of data.

  • Use the filter to narrow in on the potential issues (shown on right). 3

Flow: Run History

Here is the complete run history for a Flow

Here is the complete run history for a Flow

Flow: Run History Filtering

Filter your Flow “Run History!

Filter your Flow “Run History!

What’s great about this screen is that you can click on one of the runs and see exactly where it failed. However, opening and closing a bunch of Flows to analyze your failures isn’t always an effective way of analyzing your data. This leads to our next tip…

Tip 4: Export a Flow Run History View to a CSV File

You can export the View of Run History by clicking on the Get a .csv file link on the Run History screen.

Run History > View > Get .csv file

Run History > View > Get .csv file

The .CSV output reveals the details about the Trigger and all of the Actions within your Flow including important details like:

  • Run Start Time

  • Run End Time

  • Run Status

  • Run Error Message

  • Run Link

  • Details for each Action:

    • Status

    • Inputs / Outputs (json)

    • Start Time

    • End Time

  • And More! …

The CSV files are great because they allow you to leverage the power of Excel to analyze the deta across a series of Flow runs at once.

Conclusion

Hopefully this post will help you troubleshoot the failures in your Flows a little more quickly and easily! Good luck and happy Flowing.