cancel
Showing results for 
Search instead for 
Did you mean: 

Stop turning off infrequently used Flows

As per my post here, I have some Flows that are important parts of business processes but rarely used. I need a way to "opt out" of having these automatically disabled. Re-enabling them only turns them back on for a bit until they get disabled again (it seems like about a week), unless they are used. This is a production environment - I can't just add and remove dummy data to trigger these so that they stop getting disabled.

Status: Declined

I have consulted the Power Automate team on this issue and they have marked this issue as Declined as most of the comments relate to customers who are not paying for a full plan. Please be aware for business-critical enterprise scenarios, the product team recommends purchasing a standalone Power Automate license listed in Pricing | Microsoft Power Automate. This will ensure your flow isn’t turned off due to inactivity. 

Comments
Jameson
Regular Visitor

Why isn't this fixed yet?  It's ridiculous to have to go in and re-enable a yearly run flow every 90 days.

AnnaChu
Administrator
Status changed to: Declined

I have consulted the Power Automate team on this issue and they have marked this issue as Declined as most of the comments relate to customers who are not paying for a full plan. Please be aware for business-critical enterprise scenarios, the product team recommends purchasing a standalone Power Automate license listed in Pricing | Microsoft Power Automate. This will ensure your flow isn’t turned off due to inactivity. 

Scott_Wightman1
New Member

Thank you @AnnaChu that was the missing piece of information I didn't know.

 

It is unfortunate that Microsoft sees fit to force small customers to buy 5 of those licences as a minimum when often it is only 1 or 2 flows that are long term that require such a license.

 

Seems to be a little punitive to their smaller customers which sadly is not a new thing with Microsoft.

max81
Kudo Kingpin

@AnnaChu : sorry, but this is really disappointing. 

I don't understand why deactivating not-running flows make sense. I assume, that the workaround for many users will be to let their flows run several times unnecessarily.

 

ITCowboy
Advocate I

OK, so what I am hearing is that this is declined. The reason they stop infrequently used flows is to save process time. So instead of having a flow sitting there rarely used, and not using process time, I now need to make a flow that runs automatically to keep the unused flow alive, thereby using more processing on a regular basis.

Or, i can spend a major amount of money to have a license for a flow, so it will not die. 

 

Microsoft, once again, you are attempting to extort money from the little guys, and making no sense at all. Thanks for nothing.

Pion_G
Helper I

@ITCowboy 

The reason they stop infrequently used flows is to save process time.

What could be particularly stupid: the process dedicated to check all dormant flow to disable them could even consume more processing time that letting them active (doing nothing)

mike_face
New Member

Too bad they don't just consider allowing us to set an approximate run(s) per amount of time for the flows. This would eliminate both issues, seldom used flows would only poll and process intermittently saving processing power and allowing us to more accurately tend to semi annual event flows.

 

But instead.......Let the creation of extra flows commence so we can keep on keeping on!

Jameson
Regular Visitor

The additional purchase of a flow license, despite having every user in our org licensed with E5, to have a flow stay alive to once a year to set a value from X to 0 in a list is absurd.