Showing results for 
Search instead for 
Did you mean: 

Turning off Flow and turning back on still create new instances of Flow


Currently we are working on a bunch of flow automation logic with SharePoint connectors. The issue we have is that flow queues SharePoint list item changes even when the flow is turned off. Since we have many SharePoint metadata that are updated in bulk while testing, there are many flows that are triggered on error data after turned on. We don't want this to happen. When we turn off the flow, we want it to not run later.

When we turn off the flow, we want it to not run later.

Status: Under Review

Thank you for the suggestion. As is covered in the comments this is not a bug but an important feature to avoid data loss -- this allows you to temporarily disable a flow, make corrections, and then enable the flow, running it over all of the events that happened in the interim. Without this functionality all of those business critical events would be lost.


That being said, there may be scenarios where you want to explicitly discard your business data -- to support that case we'll look at adding an option to delete the trigger data so you can start again from scratch.

Frequent Visitor

Add me to the list. I have a Flow that only needs to run for about 2 months of the year, and I turned it off for the other 10 months. I just turned this flow back on last week, and it proceeding to run off of 10 months of modifications, in turn, crashing a server I was integrating with as part of the flow, because it got slammed with 40k requests all at once as soon as I turned it back on.

Frequent Visitor

Just got Burned by this. Looking to get this resolved as well. RIght now i pretty much will need to make sure i have trigger conditions on my SharePoint Triggers to be sure these dont kick off when the flow is turned off. 
there should be a second Off Button or on button that would have this run items behind the scenes or dont run at all. pretty much the only way to resolve this is by deleting the flow and adding it back as a new flow.  

Helper I

@kritchensBMcD You don't need to delete it. Just modify the below so the first action is a terminate. Keep the rest of your flow under that. Do the things you need to do and then you can we remove the terminate action.

Frequent Visitor

@chiguypaul that really wouldn't work. So here's my scenario.


I created a Flow that would autonumbering List items that are newly created.

I turn off that flow.

I then Load this list with its initial list of items.

Then I turn back on the flow so that it would work on NEW created items not ones already loaded.


The problem right now is that the flow will run on the items loaded into the list as soon as you turn the flow back on with  the flow being off. 


Right now i added a condition so that there is a column that gets checked so it wont trigger anymore. But the expectation for this stuff is that OFF means OFF not Off Meaning Delayed. its very very unclear that off doesnt mean off on flow. 


The only options really are:

  1. add safeguards to limit how it triggers
  2. make a copy of the flow and don't turn the copy on until you are ready to implement the flow.

MS should be clear that off doesnt mean off on flows in the interface.


Regular Visitor

@Stephen are y'all serious with this?  It's been YEARS that this has been known, and I just got burned by this.  It takes ZERO effort to add a prompt when turning the flow back on that it will run on all items in queue, and to give a count of those items.  So preventable, what are y'all doin????


Furthermore, I should also be able to dismiss those updates, this is not hard stuff to program.  Y'all are clownin, FIX THIS!

Advocate IV

Seriously, is there any update here? This is so badly needed. It's ridiculous to have to modify the flow to prevent it from running when it gets turned back on, and then modify it again.

Frequent Visitor

Been 4 years since originally requested and it is still under Review.

This is very important for some scenarios where we don't want to trigger flows.

Helper I

All I have done several test, The workaround that I’ve  use for my scenarios to fix it is to turn off the automate and point the trigger to a none use sharepoint site and turn it back on. Fix whatever is needing to be fixed with the flow or site. Once complete, point the trigger back to the original location and turn on. 

Hope this helps 

Helper V

@MP_Squared Good idea, but we shouldn't have to workaround such a basic development error by Msft. Obviously pending runs are queued somewhere, so we should be able to view that and cancel if desired. Unbelievable that Msft has done NOTHING about this when it's so obviously their responsibility..

New Member

5 years under review? Please add two field:
deactivate permanently (no records of changes)
and a field
deactivate temporally (records of changes)<


Problem solved in 3 Minutes. Please write me a check. Contact me for my bank account informations.