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: Power Up

Re-iterating it again , this is a serious issue which needs to be addressed. This is quite similar with scenario posted by JeffWhite and 980Panama

Scenario on When an Item is Created

  1. Made a copy of the Production environment flow as (Prod-Test Flow)  for the maintenance activity. 
  2. Turned off the Production flow and made small change of updating email recipient to self in the copied Prod-Test Flow to validate the small functionality.
  3. Turned on the Prod-Test Flow.
  4. Created list item 
  5. "Prod-Test Flow" got triggered (received the expected email and this was supposed to be end of test)
  6. After 2 and half minutes I turned on actual Production flow.
  7. Unexpected behavior - Production Flow ran successfully and triggered email to all business users which was not at all expected behaviour.  
  8. Need to understand the exact wait time, as same exercise has been done except the duration of turning on time was more than 5 minutes and it worked as expected. 
  9. What conditions are applicable in this scenario as per 
Level: Powered On

@dbro that's a create work around thanks!


I would like to voice my frustration with this "feature" as well. I was migrating content for historical reasons only to a list. I turned off the Flow foolishly thinking that this would in fact turn off the Flow, migrated my content, then proceeded to send out 50+ emails. The worst part is these were for awards, so I have to go back and email people letting them know that they did not in fact get a second round of awards. I was just ignorant of this "feature". 

Level: Powered On

I have a real crazy suggestion for @Stephen , why don't you call the feature what it actually is?


What does it do? It pauses any new flows from triggering and queues them for later execution". So call something like that! And for the "Turn off" feature - make it actually turn the flow off. I know, crazy!


That way us poor IT Pros don't spam our C-level suite and VP's with the risk of loosing our jobs (ok, a little dark there but read the stories in this thread...)