web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Flow updates an increa...
Power Automate
Answered

Flow updates an increasing number of items instead of only the triggering item

(0) ShareShare
ReportReport
Posted on by 4

Hello,

 

I am looking into migrating from SP 2013 to SP online, where many of our lists use SP 2010 workflows. I have migrated one list using the MS SharePoint Migration Tool. No issue there.

Afterwards I created a flow with the 'when item is created/updated' trigger. In the 'Update item' action I provide the ID from the trigger like so:

 

scr.PNG

 

When I save an item after creating the flow, that one item is updated, which is correct. When I save a second item, that item is updated correctly. But at the same time the previous item I updated also triggers the flow. When after this I update a third item, the item I just saved along with the two previous items trigger the flow at the same time.

 

Note that this is a list with already existing items. The flow is not triggered for items which were updated (migrated) only before the creation of the flow.

 

I have just created a new item, which triggered the workflow, and all three items I updated previously also triggered the workflow. Older existing items are still unaffected.

Categories:
I have the same question (0)
  • Verified answer
    ScottShearer Profile Picture
    25,277 Most Valuable Professional on at

    @KatalinDer 

    You are likely experiencing two issues.  First, there is no trigger that fires only when an item is modified -there are triggers for when an item is created and one for when an item is created and changed.  

    It also sounds like you are experiencing an infinite loop.  If a Flow runs when an item is modified and you update the item in that Flow, you have an infinite loop where one Flow causes the next to fire.

    I wrote blog posts showing solutions to both of theses issues: https://o365scott.blog/

    The two latest blog posts should show solutions to your issues.

     

     

  • KatalinDer Profile Picture
    4 on at

    @ScottShearer thanks for the input. Coming from SP on premises with only 2010 workflows, flow on SP online with its 5 minute flow trigger was just a bad scenario to troubleshoot and from how I experienced this I did not think it would be the issue you mentioned, even though that was coming up in all of my searches. Indeed adding an extra condition into the flow solves the issue. 

  • v-bacao-msft Profile Picture
    on at

     

    This is a great way to solve this problem that has long plagued us.

     

    Best Regards,

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Leaderboard > Power Automate

#1
trice602 Profile Picture

trice602 398 Super User 2025 Season 2

#2
David_MA Profile Picture

David_MA 323 Super User 2025 Season 2

#3
Expiscornovus Profile Picture

Expiscornovus 183 Most Valuable Professional

Last 30 days Overall leaderboard