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.




Level: Powered On

When triggering on a SharePoint list/lib for modifed items it would be nice to be able to update the triggered item in the Flow without the Flow re-triggering on the update. Much like a system-update.

Level: Powered On
Agree, a common usage example is a quality document management system when you want item properties updated after the approval.
Level: Powered On

As much as I'd love to see this feature, I doubt it will be implemented. This feature would be related to SharePoint team and not the Flow team. Since the beginning of the CSOM SP team was asked to implement it but never did, so I doubt they will change their minds now. 

Level: Powered On

Yes, please either prevent Add/Update flows from triggering other flows, or make it an optional check box.

Level: Powered On

This would be a greatly appreciated feature; although putting conditions in place will stop multiple flows completing it feels like a hacky approach at best!