Showing results for 
Search instead for 
Did you mean: 

Disable Event Firing when Flow updates a SharePoint list item

Add a feature that will allow flow to disable event firing when updating a SharePoint list item, so that the Flow doesn't get stuck in a loop. Currently if I create a flow with a SharePoint list trigger when item is created or modified and have the Flow update a field in the item the loop gets stuck in a loop. One workaround is to add logic to check if the field(s) still need to be updated and if not then don't update the item but even in that case the flow will be triggered twice. It just makes sense to have an option that will allow Flow to update an item without triggering an event that will cause the same Flow or another Flow to run against the item again.

Status: Declined

Hi all,


After thoroughly reviewing this idea, we have decided not to proceed with this idea for a couple of reasons.

  • SharePoint events are no longer event receiver based and are performed using webhooks or polling where applicable
  • Other Office 365 applications and internal systems like auditing may and will rely on such changes like updates to items, files and other entities in SharePoint

However, that said, we understand the crux of the issue which is to help avoid loops. We will work with the flow team to come up with a generic model/pattern that applies across data source/connections for similar scenarios.


Thanks all for your input and please submit/vote your ideas as we are actively monitoring the ideas forum.




Advocate IV

What a joke! Here I am over 2 years after this post was created and this is STILL an issue. I just ran into it with a Flow I've been working on for a while. I've got a SP list that has a column for each item to link to a document in another document library. When the document is created by this same flow in the other document library, all I want to do is update the column in the SP list with a URL that points to the document related to this item. Every time my flow updates the URL on the SP item, the flow is kicked off again. Why is it that this worked so well with SP workflows but now is a nightmare with flows? What do you imagine people doing with your product? You dare to charge people for premium licensing for certain connectors in this product? This is horrid. If you weren't MS and didn't already have your foot in the door of every single household in the world you wouldn't be able to get away with such laziness.

Advocate IV

@Gristy Looks like this isn't the first time you've gaslit people on this thread about their legitimate issue with this product. I won't waste anymore energy on you. Is this how you get to "Super User II" rank here? Man, that speaks volumes about this community.

Regular Visitor

@Gristy - I'll admit @Sparrowhawk could have been a bit more diplomatic - but I also found that stopping a flow in SharePoint realising that it was itself that caused the trigger was an enormous pain in the neck for a relatively non-technical user like myself.


I too would have hoped that the intervening 2 years would have given Microsoft the opportunity to come up with something workable - or at the very least publish some clear guidance on how to work around the limitation.



Resident Rockstar

yea i do agree its quite annoying, i had found one environment that had 150k flow runs last month due to this very problem. the de-coupling and the way the whole platform is setup, i think trigger conditions will be the best outcome. they have added a warning now if the designer detects that you will run into a loop for each instance to prompt the user.

Not applicable

That's exactly the whole point of this thread. This technology is meant for business users. Most don't think like programmers. This issue creates frustration, confusion, and a barrier for usability.

Advocate IV

@AndrewMoore I don't feel the need to spare the feelings of MS Power Automate and Microsoft as they are a product and a corporation, respectively, not human beings. I'll let you go re-read those posts and see who insinuated someone was being lazy rather than offer a useful contribution (hint, it wasn't me).

Regular Visitor

Oh dear


I'm forever baffled by how tetchy Internet forums can be. @Sparrowhawk - I'm on your side, my friend!


And yes, @Gristy , I got close to solving my problems with Trigger Conditions - but the expression needed had a daunting level of parentheses for an old timer who learned BASIC in the 1970's. Hopefully, Microsoft can slap a more user-friendly interface on that functionality for us mere mortals.


Kudo Collector

Also supporting @Sparrowhawk and agree very mich to AndrewMoore... and totally disagree to 



Yes, this can happened fast.

Frequent Visitor

I am moving from Nintex to Power Automate so I am very new at this and currently hunting a solution to stop the looping issue.  I have a workflow that kicks off when a new item is created but it causes my second workflow when a new item is created or modified and just keeps looping.  Everything I have tried seems not to work and it almost seems like the "created or modified" workflow kicks off before the "new item is created" as I start getting the emails from the "created or modified" a few times before I get the email from "new item is created".  Any help or direction to a solution would be greatly appreciated.

Resident Rockstar



There is a new trigger when item or file is modified which will kick off only when an item is modified which may be of use to you. If that is not suitable happy to help you resolve but would need more detail.