cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Fredrik_Olofsso
Frequent Visitor

Disable flow auto off after 60 days with no runs

Hi

Is there a way to turn off or disable that Power Automate turns off flows that not has run for 60 days?

 

Screenshot 2020-10-20 at 08.45.48.png

1 ACCEPTED SOLUTION

Accepted Solutions
Jcook
Most Valuable Professional
Most Valuable Professional

Hello @Fredrik_Olofsso 

 

This feature rolled out with a bug, the product group has been notified. Even button and scheduled flows through trigger annually, quarterly, are being disabled.

 

a fix should be rolled out hopefully soon


Did I answer your question? Mark my post as a solution!

If you like my post please hit the Thumbs Up


Proud to be a Flownaut!


Check out my blog for Power Automate tips,
tricks, and guides
FlowAltDelete





View solution in original post

31 REPLIES 31
Jcook
Most Valuable Professional
Most Valuable Professional

Hello @Fredrik_Olofsso 

 

This feature rolled out with a bug, the product group has been notified. Even button and scheduled flows through trigger annually, quarterly, are being disabled.

 

a fix should be rolled out hopefully soon


Did I answer your question? Mark my post as a solution!

If you like my post please hit the Thumbs Up


Proud to be a Flownaut!


Check out my blog for Power Automate tips,
tricks, and guides
FlowAltDelete





Thank you very much for a quick and good answer Jcook.

This was a button triggered flow. We will cross or fingers that a fix is coming son 😄 

JoshPedersen
Regular Visitor

Has this been fixed or still outstanding? I have some flows that could possibly have months between triggers and I cannot afford the time to keep checking up to make sure they are all still active!

Jcook
Most Valuable Professional
Most Valuable Professional

Hi @JoshPedersen 

 

This has not been fixed yet. In the meantime just watch out for the emails from Flow. You will receive a email 7 days before the Flow gets disabled.


Did I answer your question? Mark my post as a solution!

If you like my post please hit the Thumbs Up


Proud to be a Flownaut!


Check out my blog for Power Automate tips,
tricks, and guides
FlowAltDelete





I've gotten a number of these emails.  I manually turn the Flows back on.  Does this reset the 60 day period?

Jcook
Most Valuable Professional
Most Valuable Professional

Hi @jonwaite 

 

Yes from what I have seen this will reset it.


Did I answer your question? Mark my post as a solution!

If you like my post please hit the Thumbs Up


Proud to be a Flownaut!


Check out my blog for Power Automate tips,
tricks, and guides
FlowAltDelete





teqs
Kudo Commander
Kudo Commander

Any News on this? I got such a email today and I am pretty surprised by the mail. We have some flows for forms and such things, they are triggered when someone use it and it would be a problem when they got not triggered. Is there any option to shut this (in my opinion stupid default) "feature" off?

It make no sense for flows which are triggered by forms or other things which are e.g. used quarterly.

MSTill
Frequent Visitor

I think the entire idea of turning off Flows after a certain period of inactivity is a major league annoying "bug". Obviously I am not the only one that thinks it's useful to automate rare events. I have approval workflows for controlled quality management documents and the revisions of these aren't evenly spread over time but come rather in clusters with long periods in between. Relying on the email notifications is also a hassle as I am constantly spammed with messages from Power Automate providing me with useless or even wrong Information. Frequently I receive messages that there has been an unusual number of failures in the past week, occasionally referencing flows that have not run for a month or even longer (says so in the run history).

MSTill
Frequent Visitor

I have found a cool and simple solution:

How to automatically re-enable flow using Power Automate - MoreBeerMorePower (hatenablog.com)

Basically it is a flow triggered by the automatic email notification about the flow having been shut down. From the body of this email the flow and it's environment are extracted by a series of nested splits and then used as input for the "Turn on flow" function. However, there is a typo in the article.

It reads:

 

Finally, turn on the flow using Power Automate Management action. The action has two inputs, environment name and flow name, which can be obtained by split result string in previous Compose:

Environment

split(outputs('Compose_-_extract_url'),'/flows/')?[0]
Flow

split(outputs('Compose_-_extract_url'),'/flows/')?[0]


 The lower split for the Flow entry should be instead:

Flow

split(outputs('Compose_-_extract_url'),'/flows/')?[1]
Tried it out and worked like a charm... 

relseh
Advocate I
Advocate I

For the love of God fix this FFS Microsoft. This is pathetic that it hasn't been fixed in 3 months! Get off your collective lazy butts already! This isn't free Google crap, this is licensed software. You don't get to bungle an update and leave the resultant mess to your paid clients for extended periods of time without backlash. 3 months is long enough. Get it together, or stop pretending the product is ready for primetime.

UdayAdhikari
Most Valuable Professional
Most Valuable Professional

All, adding some information that was recently shared by Microsoft...

 

This is by design and not a bug; if flows have no activities (run, edit etc.) they are turned off after specific days. However, if the flow is running under paid Power Automate SKU (not acquired from O356 SKUs) license this does not apply, meaning the flow will stay active beyond 60 days.

 

I have few quarterly flows and running into the same dilemma. Hope this brings some clarity.

 

Part of the conversation with Product Team:

 

First -  we have noticed a lot of users try out flows, to never come back – these flows keep running in the background – providing zero customer value – while running meters on the Power Automate side of things.

Second – as we start getting closer to enforcing API limits, we want to ensure that users don’t have flows that are drawing down capacity without their knowledge. This can happen if you have frequently polling triggers – that don’t result in any action executions.

Third – a small percentage of our user base – sometimes ends up misconfiguring their triggers such that they never fire, and will never run an action.

 

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

Thanks

 

UdayAdhikari
Most Valuable Professional
Most Valuable Professional

And just found the link that covers what I explained above:

https://docs.microsoft.com/en-us/power-automate/limits-and-config#expiration-limits

Thank you for explaining.

 

This is a really stupid decision by Microsoft. So quarterly flows now can't work? They cannot be serious? Do Microsoft, never do anything quarterly...(joke)...?

 

So we are allowed to automate things, just not things that we don't do that often. The reason I wanted to automate these things, is because I do them infrequently and so it is a hassle as it's not fresh in my mind. 

 

I spent ages getting my Flows working and before they have even run for the first time, they are being disabled. 


@FlatOut wrote:

This is a really stupid decision by Microsoft. So quarterly flows now can't work? They cannot be serious? Do Microsoft, never do anything quarterly...(joke)...?

 

So we are allowed to automate things, just not things that we don't do that often. The reason I wanted to automate these things, is because I do them infrequently and so it is a hassle as it's not fresh in my mind. 


Exactly!

I can't believe some decisions, which are made for Power Automate (MS Flow). We are a small company and I think there are often flows, like forms for vacation requests, which sometimes are not used more than 60 days. I really can't believe this crappy decisions of MS.  There should be a simple option to "PREVENT a flow from auto disable". Just that simple.

 

PLIVING
Advocate I
Advocate I

With Covid, there are tons of exceptions this past year and some processes aren't getting done as often as before.  This really needs to be addressed.  I see the point about test flows and such wasting resources, but many of us have legitimate production flows that simply may not run very often.  One example is an alert for classroom checks that I created when equipment is not working.  We may go several months without an issue, so the workflow won't get triggered, but it will most certainly need to trigger when there is an issue.

relseh
Advocate I
Advocate I

Agreed wholeheartedy @PLIVING !

Microsoft needs to change this process ASAP.

 

We (like many others) have flows that only trigger during a specific time frame each year when customers are allowed to submit a particular form.  We have a flow that only triggers when someone submits an idea for approval, or submits a new event for the corporate calendar, and MONTHS can go by between submissions. We have flows tied to a Power App to enable mass updates to data used in the app that are only required when someone leaves the org and their records needs to be reassigned. All of these instances are sporadic, or have small time windows, but *I* do not have time as an admin to review umpteen emails about flows at risk of being disabled (or which HAVE been disabled) simply because they have legitimately been inactive for a time.

Additionally, re-enabling a flow that that Microsoft disabled due to inactivity DOES NOT WORK. The next time their system checks for inactive flows (as soon as a week later in my experience) it will be disabled again.

Microsoft needs to re-evaluate this process and at the very least give us the ability to indicate that the flow is still valid even though it hasn't been active. Send the emails about inactivity and let us check a box that says "I am not using this flow, disable it" or "This is still an active flow, keep it enabled". Even if I had to do that every 90 days it would be better than the flows we require to do business being disabled on us just because there's no need to trigger them at the moment.

mlavender
Frequent Visitor

I received a notification today that one of our flows will be disabled because it hasn't triggered in the past 90 days. Why is Microsoft automatically disabling flows?  This doesn't make any sense.

walkers
New Member

Is there any ETA on a fix for this issue????

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24  17 @Anil_g  7 @ManishSolanki  13 @eetuRobo  5 @David_MA  10 @VishnuReddy1997  5 @SpongYe  9JhonatanOB19932 (tie) @Nived_Nambiar  8 @maltie  2 (tie)   @PA-Noob  2 (tie)   @LukeMcG  2 (tie)   @tgut03  2 (tie)       Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate  @Deenuji  12@ManishSolanki 19 @Anil_g  10 @NathanAlvares24  17 @VishnuReddy1997  6 @Expiscornovus  10 @Tjan  5 @Nived_Nambiar  10 @eetuRobo  3 @SudeepGhatakNZ 8     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22   Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2   Anil_g2   SharonS2  

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (5,012)