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
TripHazard
Regular Visitor

Please Microsoft do this now - it is frustrating to our clients who need automates that run very infrequently but serve very critical purposes when they do need to run!

EdviconEdu
Advocate I

Agreed! Didn't know this is already posted. This is really a headache. 

 

I also created a post for this: (1) Stop Auto Turn-Off for a Flow if not used for a pe... - Power Platform Community (microsoft.com)

PriyaKodukula
Microsoft

For enterprise scenarios, we recommend you buy a standalone Power Automate license listed in Pricing | Microsoft Power Automate. This will ensure your flow isn’t turned off due to inactivity. 

 

Based on telemetry, 99.9% of these users are going to stay inactive forever. This is to reclaim costs from those forgotten flows. These reclaimed costs can then be applied to flows that are active / used (e.g. by keeping the API limits higher, allowing unlimited flows etc.). This will enable admins to manage licenses effectively.

The following licenses are intended for personal productivity and will be impacted by this feature: 

  1. O365 plan 
  2. Free plan- MSA and work accounts 
  3. Community plan 
  4. Trials – Power Automate, Dynamics  

Even within these plans, if the flow is an instant flow/triggered by Power Apps, those flows are excluded from being turned off. 

 User flows with the following licenses will not be impacted: 

  1. Power Automate standalone licenses – Per user, per user with attended RPA and per flow licenses listed in Pricing | Microsoft Power Automate 
  2. Dynamics licenses- Dynamics 365 Enterprise plans, Dynamics 365 Professional plans, Dynamics 365 Team Member plans 
  3. Power Apps licenses – Per user and per app licenses listed in Pricing - Power Apps (microsoft.com) 
  4. Grand fathered Power Automate licenses (P1 and P2) 
TripHazard
Regular Visitor

@PriyaKodukula How are the enterprise licenses effected? E1, E3, E5?

 

bmercer
Regular Visitor

Whenever a vendor says a feature is intended to allow me to "manage licenses effectively" I know I'm gonna be reamed on the price.

 

 

 

 

max81
Kudo Kingpin

@TripHazard O365 plans are E1,E3,E5 plans

 

@PriyaKodukula : Sorry, but that information makes no sense for me:

"Based on telemetry, 99.9% of these users are going to stay inactive forever. This is to reclaim costs from those forgotten flows. These reclaimed costs can then be applied to flows that are active / used (e.g. by keeping the API limits higher, allowing unlimited flows etc.). This will enable admins to manage licenses effectively."

--> I have also in personal productivity use cases that are not triggered really often. So it makes no sense to by therefor a standalone license.

--> I create flows always in a way that they are not triggered really often to reduce api calls. I'm using trigger conditions for example. This saves costs for me! But these flows are turned off and I have to create a workaround inside that they are triggered more often so they are not disabled? That causes costs (/api requests).

--> 99.9 %  stay inactive? how can you tell? I assume that most of the companies use the Power Platform only for a couple of years. Depending on the use case, a flow sometimes need only to be triggered every second year or so.

 

My feedback to Microsoft: please create more usefull functions for admins in the admin portal. They can than check for suspended flows etc. and clean the system, get in contact with the creators and so on.

bmercer
Regular Visitor

I'm baffled to think how an event that triggers once per year represents a significant load on anything, never mind the fact that the workarounds required to avoid this silly limitation end up triggering much more often.

 

Is Microsoft seriously claiming that the less frequently we use the service, the more we should pay for it?

 

Would be nice if Microsoft were to stop following the Marketing people and start listening to engineers again.

 

 

boredbeard
New Member

@bmercer 

 

Its because they didn't update code in source systems like SharePoint to raise an event when one occurs instead their PowerAutomate solution often polls the underlying site looking for changes. This costs them every time they don't detect a change. They are passing the cost of that poor implementation choice on to you. 

AnnaChu
Administrator
Status changed to: Completed

Please review the documentation here on expiration limits for flows: Limits and configuration - Power Automate | Microsoft Docs

bmercer
Regular Visitor

How is this "completed" when the issue is unaddressed?

If your intention is to not fix the issue, then don't say you've fixed it by not fixing it.