Created or modified flow triggered for all rows when enabled

[greddin]

I have two SharePoint lists. I created a flow that creates or updates list 2 whenever a new item is created or updated from list 1.  I tested the flow by creating a new item in list 1.  Issue is the flow was triggered/ran for all items in list 1 - where I only expected it to create the one I had just created.  It did, but also updated all the existing rows.  

How do I keep a new flow from going through all the records when I enable it? It should only trigger if I create/edit a list 1 item. 

Thanks

[FLMike]

Hi @greddin 

Please share your actual flow. The flow will not trigger for all rows just because you created 1, so that means something else is happening and honestly cannot tell since I see no details or flow. Please add that so we can help.

Cheers
If you like my answer, please Mark it as Resolved, and give it a thumbs up, so it can help others
Thank You
Michael Gernaey MCT | MCSE | MCP | Self-Contractor| Ex-Microsoft
https://gernaeysoftware.com
LinkedIn: https://www.linkedin.com/in/michaelgernaey

[greddin]

Hi, here is the flow.  The Condition checks to see if Calendar ID is null.  One list is a normal SP list and the other is a Calendar list.  The idea here is to create a calendar event entry when the first list's Calendar ID is null or update it if not.  After a calendar list event is added, it updates back to the first list with the Calendar ID.  My issue is that when I enabled the flow (off to on) it started going through all the existing list items when I expected it to only process if I edited an existing or created a new one.

Thank you for the help.

[FLMike · Accepted solution]

Hi @greddin 

I have to say... unless its the issue (I found with another user and descibe at the bottom), I dont see anything in your flow that should cause that, unless something ELSE is running you dont know about.

Firstly thank you for sharing. I Apologize I should have already asked this from you, but you said that when it triggers once, it runs for ALL rows. 

Now I know I said that cannot happen, but I did have one other person who had that. BUT we may not have the same situation.

So here are my follow ups (again apologies, didnt hit me until now)

1. Did you use a template to create this flow? (They did and it was the issue)

2. I notice that you are using Get Item. Is that simply so you can use the ID in the Get Attachments? I only ask as the Trigger has the ID so you may or may not need to do Get Items

Ok my ask is, can you verify, in the run history, that when one is created, that it triggers the other rows , like if you go look at the ID its different for them all? So if you have 6 rows, you instantly see 6 triggers? each one being the ID of a different row? Or is it always the same row, and we are actually triggering multiple times, due to infinite loop syndrome.

For the other person, we did in fact prove it was each row. So I had her create another simple flow, turn off the other and all it did was Trigger on create (at first), and have a compose of the ID. It only triggered 1 time.

Then I had them turn that one off, and create another with Trigger Create or Modified again with just a compose of the ID and it only triggered 1 time.

So they rebuilt manually without the template and it never happened again and no we never figured out why after 10000 screenshots etc.

Cheers
If you like my answer, please Mark it as Resolved, and give it a thumbs up, so it can help others
Thank You
Michael Gernaey MCT | MCSE | MCP | Self-Contractor| Ex-Microsoft
https://gernaeysoftware.com
LinkedIn: https://www.linkedin.com/in/michaelgernaey

[greddin]

Thanks for the reply Michael. I created this flow from a blank automated flow and yes - when I enabled the flow it started individual runs per row. I examined a few and saw that it was a different ID to confirm that it was doing multiple rows for some reason.  I quickly turned the flow off.  

I will try starting new with a simple flow and test from the the get go and slowly build it back up again.  

Thanks

[IhnoHanuschka]

Hi everybody, I had the same issue for a couple of days now. 
To me, it looked like a Microsoft bug:

Problem

* When I changed 1 row in a SP list, the flow started hundreds of time (on "when an item is created or modified")

* It actually ran for different items, not only the one created (for this, I exported the flow runs and examined the trigger responses)

Analysis

* So, I created a new flow with the same trigger and disabled the currupt one > this one only triggered ONCE

* Only difference was the view used in the trigger paramters

Kind of solution

* So, I changed the trigger parameters in the currupt one back and force, while saving in between

* Now the flow only ran once for the correct item when the list was modified.

Nothing really understandable, but mayby by experience helps others when they come across a similar issue 😉

Cheers

  Ihno