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

Quite. This is not completed. Please re-open

NicoleHarris
Advocate I

@AnnaR this is not completed. Simply explaining why it functions as it does is not an acceptable response in my opinion. Reading through the many use cases people have reported on this thread alone, this is a very common nuisance. Often you'd want to setup automation to check for things that aren't going to happen frequently, so that you can ensure the proper people are notified, or that a specific set of actions are taken, once it does.

 

Yes there are workarounds available such as creating a copy of the flow and deleting the original which only take a few minutes, but why isn't there a feature to re-activate a deactivated flow where the trigger counter restarts? That seems like the very minimal that could be done to improve this limitation. An email could still be sent to the owners to let them know it hasn't been triggered in 90 days and that it's going to be deactivated, so they know to go in and verify it's still a valid flow that should be reactivated. Just restart the deactivation cycle over, instead of limiting it to 7 additional days without a run, just for it to be deactivated again a week later. This would address the issue of "abandoned flows" while reducing the burden a little for those creating flows that will only be triggered a couple times a year. Even better, increase the deactivation counter to 180 days, with an option to reset it for another 180 days like a revalidation of sorts.

TripHazard
Regular Visitor

100 times this! This would make life so much easy and reduce the need to build flows just be used to keep infrequently used flows active - a process that creates unnecessary API calls

bmercer
Regular Visitor

If the intention is to leave this as it is and not fix it, then the status of this issue should be set to DECLINED, not COMPLETED, as COMPLETED means the change has been implemented, and this change has not been implemented. 

 

AnnaChu
Administrator
Status changed to: Under Review

Thank you for your feedback, this idea has been updated to Under Review.

NicoleHarris
Advocate I

@AnnaChu thank you.

TripHazard
Regular Visitor

Thank you @AnnaChu 

AnnaChu
Administrator

@NicoleHarris @TripHazard  You're very welcome, thank you for continuing to support this idea.

Scott_Wightman1
New Member

I'll add my voice to this ongoing problem. If MS has reason for doing this then share them but it is a pain for our customers that have important flows that may stay dormant at slower periods of the year being summarily shut down. The workarounds are sub-optimal solutions, as all workarounds are.

grumpymon
New Member

@Scott_Wightman1 more annoying is just the fact the so many request are still open after years (!!!) or we just get the same standard reply and never a correct answer. I have to use this product for my job and in the 2 months I'm using this right now I learned to hate it. IBM Lotus did a better job 20 years ago...

@AnnaChu can we get a clear statement without the corporate nonsense?