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: New
Comments
AprilTech
Regular Visitor

I work in the k-12 school sector. There are a lot of flows that don't run mid-May through mid-September due to the school schedule. Many processes wind down before school ends and start-up slowly after school starts.  

elisem
Advocate I

Please stop turning these off. We are a LARGE corporation and I am getting alerts every week of workflows being disabled!! This makes no sense and is getting very frustrating!

ONYXJas
Advocate IV

@elisem - I had the same problem and put together a scheduled flow to run every day and turn any of my flows that had been suspended back on. I cannot expect non-techie business owners of my sharepoint site to know what to do when an infrequently-used admin flow is suspended, and this makes sure all my admin flows are always ready to run when required.  This is the link to the article I found>> https://sharepains.com/2020/12/02/re-enable-flows-power-automate/

 

ONYXJas
Advocate IV

@AprilTech - have a look at https://sharepains.com/2020/12/02/re-enable-flows-power-automate/ - this post outlines how to use a scheduled flow to monitor and reactivate suspended flows automatically.  I did this for the infrequently-used flows on the SharePoint site I manage for a non-techie business team.

mike_face
New Member

Agreed, super dumb I have to spend a few mins literally everyday re-enabling flows for our systems. Heaven forbid I miss one of the notices and things crash down. Lots of form triggers in my environment, some of these forms are used during a short sign up period for the yearly event. Terrible business choice IMO. wishing i had just avoided this entire money grabbing platform.

We pay out the nose for these subscriptions we do have, and then M$ pulls stunts like this to grab even more cash. Shameful.

AprilTech
Regular Visitor

Thank you @ONYXJas I got the flow created but now I'm running into permission issues. Hopefully, my local admin will help me out with this. The account that publishes that workflow needs to have a "Global Admin Role" per Microsoft support. The environment maker was not sufficient. 

AgnesJensen
New Member

I completely agree. I have over 60 flows that are annual for reporting and the idea of automization kinda looses its point if I need to manually turn flows on. 

Eibbor
Regular Visitor

This is crazy, and dishonest marketing in my opinion. It makes all subscriptions that are not upgraded effectively 'trial-mode' because switching off someones automation should never be someone else's decision,

and there should never be a case where people were unaware this would happen.

 

Part of the use-case for automation is exactly to keep an eye on those things that seldom happen.

Part of the attraction for me is to trigger annual or rarer events and overcome human fallibility in remembering those non-routine things.

 

An additional subscription is and additional layer of complexity and potential failure too. Please consider changing this.

 

 

 

 

 

 

 

 

ONYXJas
Advocate IV

@AprilTech - I also had permissions issues, but it turned out to be because of our DLP policy.  I found that by NOT including any notification/email step so the flow runs silent, it appears to bypass the permissions issue.  It does mean you have to check the flow monitor once in a while in case of errors.