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. 

New Member

I completely agree and experience the same problem. What a supremely idiotic feature !

The feature by default should be DON'T deactivate flows. Then if we allow deactivation, we should be able to set the number of days (or years) 

Kudo Kingpin

The expiration limit is here:


But I know this wasn't the case when I initially created the Flows. Which is very frustrating - had I known this would happen, I would have been able to take that into account. 

New Member

why can't i see word online on my flow?

Kudo Kingpin
Regular Visitor

Alternatively, consider offering a workflow expiration date option on the flow's settings page, trigger, or termination action. 

Advocate I

I suspect this is a fault in their design, my understanding is a lot of the triggers actually go out and query the source for changes on a set interval of time.


This causes computation power usage that is wasted every time the trigger results in a failure.


As opposed to if it had been implemented that SharePoint or whatever service actually reaches out to flow and raise an event. In that situation no computation power is wasted on flow side while it is dormant waiting to trigger. They are probably getting their resources consumed up with all these polling queries that result in nothing happening and this is their quick fix for a poorly designed product and over selling their capacity.


While not a proper fix, they could at least just degrade service at 60 days to say check every 15 mins instead of just off and having a sliding scale that reduces to say checks once a day after 6 months but never off. Then once a trigger does occur on the once a day it returns to the more frequent checks and then decays off again in check frequency.

New Member

Totally agree!

New Member

i don't want to vote for features microsoft will move away from the family plan to higher paid  business or school accounts. wtf.

i am bit upset and will look for alternatives ...

New Member

This is a problem for me as well.  Just because it hasn't been "ran" recently or even ever, doesn't mean that we don't want it to run should the triggering event occur.  In some of my flows, the triggering event may never occur and the flow may never run.  It is impossible for me to know if someone will in the future delete a file in the libraries I am monitoring.  My only recourse is to set up an Alert and then if it ever does occur, manually do the steps my flow would do if Microsoft would stop disabling it.  I have done that in some cases

Regular Visitor

This is more than a bit ridiculous. I've built a phone-based PowerApp for safety monitoring for field staff to check in. There is also an emergency button that we hope does not get used, but alerts management and safety personnel in Teams and via email that something has happened. Since nothing has happened, I've gotten a notice that it will be shut off. Please fix this!