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.




Super User

Would like a 'Set Field' action in Flow which will not kick-off the Flow. Currently there is an 'Update Item' action available which is kicking off the workflows. What's interesting is that this can cause a loop effect which can send out continuous email notifications.

Level: Powered On

Right now when i edit an item of a sharepoint list from flow, it starts again the event "when item is edited", 
Which causes an infinite loop. this is new, yesterday it works fine. Smiley Sad

Level: Power Up

Hi Flow Team,


I'm using the SharePoint - When an item is created or modified trigger.  Within my flow I need to update data on the very same item that triggered the flow.  Doing so causes the flow to trigger again.  This is a loop condition and should be a configurable behavior.


You might tell me, as others have, to keep copies of all my list item values, and to test all those values for a difference, and then only update the item conditionally.  This is dumb.  It is not a scalable option.  It doesn't enable your user community.  It discourages adoption of your platform.


To spell it out, I have to create a 2nd column for each column for which I want to detect changes.  It is simple enough to test for changes in Flow, but the more columns I have the more tedious that is.  Then I have also to create customized New, Edit, and Display forms in SharePoint to hide these extra columns from the end users.  Adoption is limited to motivated power users, casual users are not enabled.


My best suggestion is that the action SharePoint - Update item include a Setting that allows us to disable workflow triggering.  The behavior options could be:

  • Global - Do not trigger any flows with this update
  • Local - Do not trigger another instance of the current flow with this update

I've seen this issue pop up on at least two community posts:

Please help us out by addressing this fundamental gap.




Level: Powered On

When I have a SharePoint trigger for a SharePoint List it would be good to have an option to disable any further triggers if I need to update the list from the flow.


Say for example I need to update a Status field based on the outcome of the flow, currently, if I used the SharePoint Update item to do this it triggers the flow again causing a loop.


This can be prevented with some form of field hack and conditional statement but would be great not to have to do this.


it could just be a checkbox option for the SharePoint Update Item action "Prevent further Flows from running"

Level: Power Up

The update item step is very laborious as well because it does not take account the current field values of the sharepoint list item for which the trigger runs. This means that all required fields within the update item action have to be mapped to the current equivalent item fields.