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.

Level: Powered On

I can't believe this was originally asked for back in 2017 and yet there has been no change to the way this feature works?! 


I too have  just fallen foul of this, although thankfully not to the degree that some others have. 


That being said, sending out over 1000 emails to 45 people across the business is a less than ideal outcome. 


Please, please add a fix for this, or at least change the name! 


An off switch that isn't an off switch, whatever next. 

Level: Power Up

This is causing a major issue at a large O365 migration program for a Fortune 500 organization we're working with.  Microsoft - PLEASE PRIORITIZE THIS.  This particular organization is evaluating whether to push major adoption of Flow, and it's causing a lack of trust in the Power platform.  

Level: Power Up

It is very difficult to make updates using the save as feature as a workaround as it is very time consuming. 
Please let us know if this update would be done?

Level 8



at first I was frustrated by this during migration efforts, but a simple interim fix is to add a terminate action right after your flow trigger. then it runs the flow but does not do anything.  Agreed that it'd be great to be able to choose whether the flows run with a toggle button or something.