You’re offline. This is a read only version of the page.
When a new service request comes in I have a flow which sends an email to potential service providers and asks them if they are interested in providing that service. Because many of the potential providers don't respond to the email (it is an email with a Yes/No option) I have configured a branch to run after time out and set the email to time out after 2 days. This has worked well but because there is almost always a potential provider who doesn't respond, the flow configured to "run after time out" triggers each time and completes the flow.
As far as I am concerned if this runs then the flow is a success as it has run as designed, but Power Automate marks each flow where the 'run after branch' is triggered as a failure. After so many failures Power Automate disables the flow automatically which causes all the runs in progress (around 15 are triggered each day) to be cancelled.
How can I stop Power Automate from turning off this flow?
The whole point is that for this specific case, the terminate triggers when no action is taken, after a set timeout period. Although the flow probably could stand for some design improvements (it is an old post, after all), in this case the goal is to end the flow after timeout without causing a failure, and this solves that without impacting other branches.
You're correct though that just throwing these willy nilly isn't good design, but these work basically like "exit loop" triggers when used properly
Even if you enter a terminate block at the end and set the "Reason" to success it will cause an issue given that there will be no easy indication that your flow did not run as it should have. In some cases this may work but other instances developers would have view each flow run and determine whether it had actually performed all the actions correctly.
This is an old post obviously but came across it searching for possible reasons an automation may have disabled itself. For the benefit of others: If you have a fail branch as OP does, just set up a "Terminate" block at the end, and set the "Reason" to Success (or possibly cancelled could be appropriate as well). This will avoid power automate treating the automation as a failure (since you got the expected result, meaning the automation ran successfully)
based
Hi @HMJ_Somerset ,
I'm afraid there is no way to achieve your need, you will need to turn on the flow manually.
See in below thread and consider vote for the idea linked in it:
Solved: Microsoft turned off my flow due to failures, but ... - Power Platform Community
Best regards,
#1
WarrenBelz
146,651
Most Valuable Professional
#2
RandyHayes
76,287
Super User 2024 Season 1
#3
Pstork1
65,999
Most Valuable Professional
Share
Report
All responses (
Answers (