cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
JJ_in_atlanta
Advocate II
Advocate II

Flow update to SharePoint list item fields triggers the Flow to fire again

We often use sharepoint designer workflows to set list field values that we will examine later in the workflow, when the item is updated by the user at a later time.  I just tried to to that with a Flow. The Flow triggers on item Creation or Edit, and then modifies several fields in the same list item.  I am seeing that the flow is actually being triggered lots of times - it appears to be in a loop where the updates it makes to the list item triggers the Flow again, makes more updates, which triggers it again.  Is this expected behavior? If so, is there a way around this?

31 REPLIES 31
v-yamao-msft
Community Support
Community Support

Hi JJ_in_atlanta,

 

I assume that you are using the trigger “When an item is created or modified”. This trigger will be triggered whenever an item is created or modified. So when your users update fields in the list, it will be triggered.


Not sure with your scenario. You may try to use the trigger “When an item is created”, then the flow won’t be triggered when an item is updated.


While if you want to be notified when a certain field is updated, you may consider to add a Condition in your flow to filter the flow runs.


Hope this could be a reference for you. If you need more help, please feel free post back.

 

Best regards,
Mabel Mao

Community Support Team _ Mabel Mao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Thanks for your reply, though it didn't address my question.  My flow triggers on item Create or Modify, which is what we need it to do.

What it does is reads the value of a field and then updates the value of another field in the same list item.

 

When it updates the value of that other field, the flow is triggered again because it fires On Modify - which it needs to do so that when a user modifies the item, it can update that other field if appropriate.

 

The issue is that when the flow updates the list item, the flow detects this item modification and so triggers itself again, and again, and again. Is this expected behavior? Is there some setting on the flow that I can set that says "don't let item updates made by this flow trigger this flow again"

 

thanks

Has this been fixed? 

 

When we were able to do this with C#, it was easy, just added base.DisableEventFiring() and then modified the list item programmatically. 

 

If this problem still persists, Flow is useless

Hi JJ_in_atlanta,

 

Thanks for updating.

 

The situation you are having would cause Microsoft Flow in a loop. It is a default behavior that when a list is updated, flow will detect it as a modification, so the flow will be triggered again and again. I am afraid that there is no workaround currently.

 

I will help confirm this issue on my side.

 

Best regards,
Mabel Mao

Community Support Team _ Mabel Mao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Hi Mabel,

 

I want to bump this thread.  I agree with the OP, this severly restricts what I can do with Flow.  I have an identical use case.  There might be some folks out there that need the recursive triggering as well.  The more common case I find is run the flow one time when an item is updated, to allow me to control values on that same item (by updating it within the flow).

 

Flow needs to let us disable this recursive trigger behavior.  Please escalate to the development team.  I'm going to try to figure out how to do that myself as well.

 

Thanks,

Harry

Anonymous
Not applicable

I also wanted to add another +1 for this.  This prevents me from being able to perform a true sync between Sharepoint and an external API.  I'll take any work-around available!

I guess if you add a condition after the trigger, maybe you can minimize the number of times the trigger is invoked.

I mean, as a temporary workaround.

For example, if the item is modified by the Flow Owner, then skip the rest of the Flow action Blocks.

Unfortunatelly, I haven't tested such workaround yet.

 

Did I make your day? If so, mark my response as 'Solution' !!!

También escribo sobre Power Automate en este Blog y en Twitter

Anonymous
Not applicable

Hi JJ_in_atlanta,

 

I reckon this is still an issue because i haven't seen any comment that says it has been resolved.

 

Not sure if this would help, but a possible workaround from the top of my head might be to:

1. Add a hidden field which would hold the same value as the field that is updated

2. Before updating the field, compare the value read from the original field to the value in the hidden field and only perform the update if the values are different (update the value in the hidden field at the same time)

 

I am hoping the above would reduce the number of updates to the field.

 

I may be in the same dilema soon because I just started working on a simialr trigger but a different scenario yesterday and am yet to test.

Anonymous
Not applicable

I added a condition that checks if the modified and created date are within 2 seconds of each other, and then had the process go in two different directions based on my custom connector.  That semed to work.

Anonymous
Not applicable

How would you manage that with the Flow language?

@equals(triggerBody()?['Created'], triggerBody()?['Modified'])

If created equals modified +- 2?

Anonymous
Not applicable

@lessOrEquals(triggerBody()?['Modified'], addSeconds(triggerBody()?['Created'], 2))

 

 

I had once instance where having a 1 second difference wasn't enough.  2 seems to be the magic number here. 

Anonymous
Not applicable

Thank you very much. I had no idea Flow was capable of less than or equal to.

Anonymous
Not applicable

Glad to help!

 

The interface is weird:  It will give you the boolean syntax related to numbers, but only if you save and reload the page with an integer or time field has been added.  

That won't work in my use case - each time a user edits an entry, we need to check for changes and possibly alter some list item fields - it isn't just a one-time change.  So, comparing against the created time won't help.

daniel667
New Member

Same problem for me, quite common scenario it seems.

Guess i could fall back to C#, but feels like you should not have to do that for such a simple task.

 

+1

 

 

Hi

@v-xida-msfthas published a workaround in the following thread 

https://powerusers.microsoft.com/t5/General-Flow-Discussion/Flow-running-thousands-of-times-on-SP-qu...

 

Unfortunatelly, this workaround is not universal but targeted for a very specific scenario, in which the result of item update is also evaluated in the Flow meaning it is executed twice instead of entering an infinite loop

 

These kind of "condition based" workarounds are the ones i was referring in my previous post: "I guess if you add a condition after the trigger, maybe you can minimize the number of times the trigger is invoked.I mean, as a temporary workaround. For example, if the item is modified by the Flow Owner, then skip the rest of the Flow action Blocks."

 

I totally agree it is a huge limitation in Microsoft Flow. Let's hope Flow architects will find a solution to fix it. 

 

 

Did I make your day? If so, mark my response as 'Solution' !!!

También escribo sobre Power Automate en este Blog y en Twitter

Bee
Frequent Visitor

Glad I found this post becasue I thought I did something wrong when my flow kept looping. Still no solution after all this time. I want to start using Flow instead of workflow, but I had to go back to workflow everytime because of limitations such as this one.

We have documents that need to be altered if they are rejected.

They go through 3 different approval processes - when they are declined or accepted the message is stored on the list as a comment from each approver. 

 

The list gets updated and the trigger starts again - but I need this Modfied trigger as the user will modify the document to make changes to go through the process again.

 

Am I doing something wrong, maybe using the wrong Flow ?

 

 

Anonymous
Not applicable

Can you provide more details on how you accomplished this, please?

Helpful resources

Announcements

Check out the Copilot Studio Cookbook today!

We are excited to announce our new Copilot Cookbook Gallery in the Copilot Studio Community. We can't wait for you to share your expertise and your experience!    Join us for an amazing opportunity where you'll be one of the first to contribute to the Copilot Cookbook—your ultimate guide to mastering Microsoft Copilot. Whether you're seeking inspiration or grappling with a challenge while crafting apps, you probably already know that Copilot Cookbook is your reliable assistant, offering a wealth of tips and tricks at your fingertips--and we want you to add your expertise. What can you "cook" up?   Click this link to get started: https://aka.ms/CS_Copilot_Cookbook_Gallery   Don't miss out on this exclusive opportunity to be one of the first in the Community to share your app creation journey with Copilot. We'll be announcing a Cookbook Challenge very soon and want to make sure you one of the first "cooks" in the kitchen.   Don't miss your moment--start submitting in the Copilot Cookbook Gallery today!     Thank you,  Engagement Team

Announcing Power Apps Copilot Cookbook Gallery

We are excited to share that the all-new Copilot Cookbook Gallery for Power Apps is now available in the Power Apps Community, full of tips and tricks on how to best use Microsoft Copilot as you develop and create in Power Apps. The new Copilot Cookbook is your go-to resource when you need inspiration--or when you're stuck--and aren't sure how to best partner with Copilot while creating apps.   Whether you're looking for the best prompts or just want to know about responsible AI use, visit Copilot Cookbook for regular updates you can rely on--while also serving up some of your greatest tips and tricks for the Community. Check Out the new Copilot Cookbook for Power Apps today: Copilot Cookbook - Power Platform Community.  We can't wait to see what you "cook" up!    

Welcome to the Power Automate Community

You are now a part of a fast-growing vibrant group of peers and industry experts who are here to network, share knowledge, and even have a little fun.   Now that you are a member, you can enjoy the following resources:   Welcome to the Community   News & Announcements: The is your place to get all the latest news around community events and announcements. This is where we share with the community what is going on and how to participate.  Be sure to subscribe to this board and not miss an announcement.   Get Help with Power Automate Forums: If you're looking for support with any part of Power Automate, our forums are the place to go. From General Power Automate forums to Using Connectors, Building Flows and Using Flows.  You will find thousands of technical professionals, and Super Users with years of experience who are ready and eager to answer your questions. You now have the ability to post, reply and give "kudos" on the Power Automate community forums. Make sure you conduct a quick search before creating a new post because your question may have already been asked and answered. Galleries: The galleries are full of content and can assist you with information on creating a flow in our Webinars and Video Gallery, and the ability to share the flows you have created in the Power Automate Cookbook.  Stay connected with the Community Connections & How-To Videos from the Microsoft Community Team. Check out the awesome content being shared there today.   Power Automate Community Blog: Over the years, more than 700 Power Automate Community Blog articles have been written and published by our thriving community. Our community members have learned some excellent tips and have keen insights on the future of process automation. In the Power Automate Community Blog, you can read the latest Power Automate-related posts from our community blog authors around the world. Let us know if you'd like to become an author and contribute your own writing — everything Power Automate-related is welcome.   Community Support: Check out and learn more about Using the Community for tips & tricks. Let us know in the Community Feedback  board if you have any questions or comments about your community experience. Again, we are so excited to welcome you to the Microsoft Power Automate community family. Whether you are brand new to the world of process automation or you are a seasoned Power Automate veteran - our goal is to shape the community to be your 'go to' for support, networking, education, inspiration and encouragement as we enjoy this adventure together.     Power Automate Community Team

Hear what's next for the Power Up Program

Hear from Principal Program Manager, Dimpi Gandhi, to discover the latest enhancements to the Microsoft #PowerUpProgram, including a new accelerated video-based curriculum crafted with the expertise of Microsoft MVPs, Rory Neary and Charlie Phipps-Bennett. If you’d like to hear what’s coming next, click the link below to sign up today! https://aka.ms/PowerUp  

Tuesday Tip | How to Report Spam in Our Community

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   As our community family expands each week, we revisit our essential tools, tips, and tricks to ensure you’re well-versed in the community’s pulse. Keep an eye on the News & Announcements for your weekly Tuesday Tips—you never know what you may learn!   Today's Tip: How to Report Spam in Our Community We strive to maintain a professional and helpful community, and part of that effort involves keeping our platform free of spam. If you encounter a post that you believe is spam, please follow these steps to report it: Locate the Post: Find the post in question within the community.Kebab Menu: Click on the "Kebab" menu | 3 Dots, on the top right of the post.Report Inappropriate Content: Select "Report Inappropriate Content" from the menu.Submit Report: Fill out any necessary details on the form and submit your report.   Our community team will review the report and take appropriate action to ensure our community remains a valuable resource for everyone.   Thank you for helping us keep the community clean and useful!

Users online (5,056)