My flows keeps being turned off constantly

[ofs]

I built important flows connected to PowerApps, Sharepoint etc and they have been working fine for years for now.

But since this month started some of them keeps being turned off & not sure why this happens. Could anybody help?

I've checked some possible cause like DLP, but my emphasis is "It's been working until this month".

Each single of my flows works an important role so it needs to work 24/7.

Is there any new management method by Microsoft that shuts down the user-built codes & apps?

Those flows in issue are shared with my team, PowerApps-based, instant type, and have connections with Sharepoint & Quickbooks Online.

Any advice are welcomed!

[v-litu-msft · Accepted solution]

Hi @ofs,

So the Flow is turn off by it automatically, right?

Did you create a Flow about Flow management to turn off a Flow?

So, how about create a Flow management Flow that checks these Flows needs to keep running. If they closed, turn it on, for example:

Best Regards,
Community Support Team _ Lin Tu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[ofs]

Sounds like a solution. I will try it out and will get back with Solution Tag to you soon. Thank you!

[ofs]

Thank you Lin, it seems working after I tested!

Regards,
OFS

[Anonymous]

Currently I have the same issue!

My flow ran for more then a year, untouched. Every day! Now it get´s deactivated after 4-5 days.

• There is no flow running, which might do this on purpose
• There are no errors within the execution
• It does not have an accidental "deactivate this flow"-condition

What have I done:

• Modify & save it
• Looking into the log, which doesn´t say anything (at least to me)
• Activate it several times

As mentioned, I can create a flow, which checks the status and activate it. But this could not seriously meant to be the solution 🤔

The February 15th, might be the first time where this happened.

[Mithlogie]

Many users in this thread : https://powerusers.microsoft.com/t5/General-Power-Automate/Flow-Turning-off-over-weekend/m-p/490786#...

are seeing the same issue. Mine also started to be turned off by themselves starting around February 15 or 16.

Maybe Microsoft should look into this.

[khoffmaster]

This should not be classified as an acceptable solution.  This does not acknowledge the root cause of the problem nor does it provide a reliable solution.  What if the flow you create to check and turn on your existing flow turns itself off?  Are we to just keep creating flows to check our flows?

[Anonymous]

I agree. There has to be a better solution. I have a flow that keeps being turned off because it did not run for 90 days. Well, maybe that is ok for the type of flow it is. I don't want them turned off. How do we prevent this without having to write another flow?

[KarlHoffmaster]

This can not possibly be the solution.  If a flow turns off automatically, building another flow to check flows is a bit self defeating.  What happens if the Flow that checks flow turns off automatically?  How many flows to check flows need to be built?  Why are they turning off?  This is no a solution, it is a work-around, and not a good one at that.

[simeonsamarium]

Have you referred to this documentation of power automate limitations: Limits and configuration - Power Automate | Microsoft Learn

Here are some excerpts:

"A cloud flow that is consistently throttled for 14 days will be turned off. The flow creator and co-creators will get an email when the flow starts throttling and when the flow is turned off. For enterprise scenarios, we recommend you buy a standalone Power Automate license listed in [Pricing article]https://make.powerautomate.com/pricing) to get higher action limits. You can turn your cloud flows back on anytime."

"A cloud flow that has a trigger or actions which fail continuously will be turned off. Fix your trigger or actions and turn on the flow."

[worldwidewind]

Another issue is that, certain triggers fail not because there is anything wrong with the flow but because we sometimes need to do things manually. For example, I have a perfectly working flow related to Bookings. There are times when my receptionist needs to manually add an appointment to my booking calendar and choose an appointment type. This causes the flow to fail because it was not booked through the booking page. The system then disables my flow saying it failed multiple times. It's very frustrating because there is no problem to fix in the flow itself. MS needs to improve this half-baked software.