cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

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

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.

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

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

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Summer of Solutions | Week 3 Results | Win free tickets to the Power Platform Conference

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24  17 @Anil_g  7 @ManishSolanki  13 @eetuRobo  5 @David_MA  10 @VishnuReddy1997  5 @SpongYe  9JhonatanOB19932 (tie) @Nived_Nambiar  8 @maltie  2 (tie)   @PA-Noob  2 (tie)   @LukeMcG  2 (tie)   @tgut03  2 (tie)       Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate  @Deenuji  12@ManishSolanki 19 @Anil_g  10 @NathanAlvares24  17 @VishnuReddy1997  6 @Expiscornovus  10 @Tjan  5 @Nived_Nambiar  10 @eetuRobo  3 @SudeepGhatakNZ 8     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22  

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (3,474)