That's the weird thing: it's only triggering once. I also checked to see if I had another flow that might be responsible (I initially tested in another environment before I realized I needed to create it IN that Team's Dataverse environment), but nothing. So, the flow only runs once, and there's only one "add row" action, but it's creating the row twice.
Hi @ChadVKealey,
My suggestion would be to have a look at the trigger action of both events in the flow history, that might give you a clue why it is triggering twice.
In the meantime it is also possible to implement a workaround. You could use a list rows action with a filter query to see if the row for the user already exists. If that action returns a result you can skip the creation of a new row.
WarrenBelz
146,702
Most Valuable Professional
RandyHayes
76,287
Super User 2024 Season 1
Pstork1
66,015
Most Valuable Professional