Power Community

Power Community

Managing high volumes of flow runs within Power Automate using Power Apps

Managing high volumes of flow runs within Power Automate using Power Apps Microsoft Office 365 image 9

When you have high volumes like 100s of flows in your environment how do you manage these flows. All these flows are kicking off whenever they need to run. It can be a challenge to find out which flows are actively running.

Finding your Running flows

When you use the standard Power Automate UI, you can see all your flows, but if you want to see if a flow is running or if a flow has failed then you will probably have to visit each flow’s run history pages.

High volumes of flows with flow runs

But each history page will only show you one single flow’s runs.

Managing high volumes of flow runs within Power Automate using Power Apps Microsoft Office 365 image 8

And you can’t easily see if all flows failed for the same reason or if there were different reasons.

Today I put a quick proto type together in Power Apps. This app can show all the running flows in your tenant, or all the failed flows with the reasons why the flow failed.

Architecture behind the high volume flow management solution

First of all to make this app work it is important that the app is scalable and that it will perform well. Handling high volumes of flows will give us extra challenges. Imagine having 10 environments or more in your tenant. Each environment may run 100s of flows. There is a lot to look at.

The system will need to check flow runs for flows that run often more often than flows that only run on a daily or weekly basis. The Pro version of this solution will check more or less often for flow runs depending on the previous flow runs found keeping the system up to date where possible.

We need to take care however not to collect flow runs for all flows every minute as that would simply not be scalable. Regular checks for flow runs using APIs need to be minimized. In my post mentioned below I will go into more detail on this.

Using the right API to get the flow runs on a regular basis and updating tables in Dataverse, keeps the Power App nearly independent of the amount of data received by the API. Further details can be found in the step by step guide to create a flow management app post.

Further ideas

The inability to search in the Flow run history is painful, hence the above app will also offer the options to search through the flow output. With this app, it should be easier to manage the high volumes of flows that you might have in your environment.

Monitoring all these flows that your users may develop. can be important. Howe about a user putting your SharePoint under that much pressure that your SharePoint site starts to perform not so well. With this solution you can identify which flows are a likely cause of problems.

Have you got any further pains that you want to share that could be solved by this app then please leave a comment below.

This post was originally published on this site

- Advertisement -spot_img

LEAVE A REPLY

Please enter your comment!
Please enter your name here

- Advertisement - Advertisement

Latest News

ON DEMAND | SharePoint in-depth: Learning content

There’s the thinking cap. And then there’s the deep-thinking cap. It’s time to put on the latter. This article contains...

More Articles Like This

- Advertisement -spot_img