Prevent unused Flows from being turned off

[hilary_stoupa]

Is there a way to prevent Flow that are rarely used from being turned off? I have a rarely used but still business critical process where there was a warning email and then the the Flow was disabled:

We noticed that your flow has not run at all in the past 90 days. We disabled it on ...

The email address for this account is not one that I check frequently, so I had not seen the warning. Regardless, this seems like something I should be able to disable.

I did see a suggestion to create an admin Flow that checks Flows to see if they are on, but I consider that to be a bit of a clunky work around.

[samsa17]

Never mind. It's actually working. The flow list on the "My flows" screen doesn't seem to update unless you click on the flow and notice it is actually turned on. 

[inspirepm]

As other mentioned, we should have the ablity to keep enabled rarely used, but business critical flows.

In the meantime, I think I will set up an auto-recurring email that will initiate the flow every 30 days. That way my flow will not be deactivated. I can add a step in the flow to not proceed with the usual steps if it is the automated email. This feels a lot simpler than the suggestion to seek out flows that are turned off and switch them to turned on.

[LyndonL]

There seems to be a decent workaround here:

https://www.portiva.nl/portiblog/how-to-bypass-the-expiration-limit-in-power-automate

[mvasiloff]

THIS...This worked fantastically well and only took 2 min to set up.  Thanks so much for the solution!

[storere]

Hi Dji,

Can you give more info on how you set this up please?

What do you mean by power automate basic? and how do I find this action?

[sajarac]

Hello @Dji , Do you know if that action still available ? For some reason I can not see the "activate flow".

Thanks in advance.

And BTW. That solution is probably the best and fast solution so far for that annoying issue.

[storere]

I wanted to post with a solution FOR THE FIRST TIME!

I'm fairly new to power automate and have learned A LOT on my own over the last 6 months so was absolutely busting when I tried an action this morning that resolved this issue for me!

I scheduled a 'Recurrence' trigger and then a 'Turn on Flow' action (it asked me to login to Flow Management).

I added a sample flow that is used infrequently by my organization and watched it turn back on before my very eyes! (see steps below):

[sajarac]

@storere , Thank you very much for this. your solution was a "SOLUTION" in deed. 

An easy way to fix this annoying "🐞 BUG"

Thanks Again!