When a List is Updated issue

[forbudt4u]

Hello, I have a flow that is working.  However, I had to modify some of the processes we were using on the PowerApps & SharePoint side of thing so I turned the flow off when working through those issues.   The issue is that when I turned the flow back on it ran the flows for all updates that took place during the entire off time duration.  There were TONS of updates and it literally locked up my SharePoint & PowerApp, so I had to turn off the flow again.  

Can someone confirm what the flow is looking at?  I have other flows that are set up under the same template (when a list item is updated) and they don't seem to follow this logic... they actually only run when it sees the update happen in real time.  I didn't think the flow would look through the entire list to see what updates meet the trigger conditions during the off-time and run all of them?? 

[jinivthakkar · Accepted solution]

@forbudt4u yes that happens because the events are queued and as soon as you turn them on, they all start to fire.

Its a data loss prevention feature by Microsoft, see this for more details :

https://powerusers.microsoft.com/t5/Power-Automate-Ideas/Turning-off-Flow-and-turning-back-on-still-...

But to help you with this situation, you can add a trigger condition for your flows, so the queued instance doesn't run, check how to add trigger condition 

https://www.youtube.com/watch?v=tlS6pSAx-GY

Going to be quite some work but I don't see a way out apart from trigger condition.

--------------------------------------------------------------------------------

If this post helps answer your question, please click on “Accept as Solution” to help other members find it more quickly. If you thought this post was helpful, please give it a Thumbs Up.

[forbudt4u]

@jinivthakkar 

Thank you for the links, and as with almost everything Microsoft does, I both understand and don't understand the logic behind why they do things the way they do.  Going through the entire 7 pages of comments, the reasons why I don't understand are only confirmed.  You would think that Microsoft would give a simple toggle choice on whether or not you want the flow queued while turned off or not.  

The good news is that even though I have roughly 30 flows, there are realistically only 5 or so that I would ever turn off.  So, it looks like I'll have to go add an impossible trigger to those. 

Appreciate the links and education regarding this issue.