cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Advocate IV
Advocate IV

How to stop new flows from starting if one is already processing?

We have a scheduled flow that checks for new data a few times an hour and a typical run takes a minute or less.  Recently the vendor reset the flag on all the data causing a few hundred rows to reprocess.  This took a few hours to complete.

 

No big deal, except that each subsquent scheduled run of the flow saw the same couple hundred rows requiring processing.  In some instances I can understand multiple flows running at the same time to be a good thing, but not in this particular Flow's case. 

 

Is there a setting available that would have the flow engine check if there is an active run, and if so, skip that schedule?  There are ways to manually track a status we could build, but I was wondering if there was anything out of the box.

1 ACCEPTED SOLUTION

Accepted Solutions
Community Support
Community Support

Hi @ bbrazeau,

 

 

Do you want to stop new flows from starting if one is already processing?

 

Stopping new flows from starting if one is already processing is not supported in microsoft flow currently,I afraid that there is no way to achieve your needs in Microsoft Flow currently.

 

If you would like this feature to be added in Microsoft Flow, please submit an idea to Flow Ideas Forum:

https://powerusers.microsoft.com/t5/Flow-Ideas/idb-p/FlowIdeas

 

Regards,
Alice Zhang

View solution in original post

5 REPLIES 5
Community Support
Community Support

Hi @ bbrazeau,

 

 

Do you want to stop new flows from starting if one is already processing?

 

Stopping new flows from starting if one is already processing is not supported in microsoft flow currently,I afraid that there is no way to achieve your needs in Microsoft Flow currently.

 

If you would like this feature to be added in Microsoft Flow, please submit an idea to Flow Ideas Forum:

https://powerusers.microsoft.com/t5/Flow-Ideas/idb-p/FlowIdeas

 

Regards,
Alice Zhang

View solution in original post

Anonymous
Not applicable

Once again, something needed as a basic requirement is not implemented.  The amount of time taken to add these basic features to the core platform and core MS products is beyond a joke.  Stop developing all the other non-MS connectors and focus on your own stuff first!

See https://powerusers.microsoft.com/t5/General-Flow-Discussion/Is-it-possible-to-wait-for-a-flow-run-to...

 

(Bascially you can limit the concurrency on the Flow trigger action to 1 - it is unlimited by default)

Advocate II
Advocate II

Hi,

 

This has already been realized in Microsoft flow. If you:

1. Go to the settings of the first step of the flow

2. Ture on Concurrency Control

3. Degree of Parallelism, make this value 1

 

Then what you want will be realized. When the first-triggered flow is running the second-triggered flow will run after the first one finishing running.

 

FlowTriggerConditions.png 

 

Helpful resources

Announcements
PP Bootcamp Carousel

Global Power Platform Bootcamp

Dive into the Power Platform stack with hands-on sessions and labs, virtually delivered to you by experts and community leaders.

secondImage

Power Platform Community Conference On Demand

Watch Nick Doelman's session from the 2020 Power Platform Community Conference on demand!

MPA Community Blog

Power Automate Community Blog

Check out the community blog page where you can find valuable learning material from community and product team members!

Users online (10,059)