I've created a flow that is triggered by a row in a DV table being added or modified. Regardless of which triggers the flow - an addition or modification - the flow runs twice, creating a duplicate entry in a child table. I've trawled through endless posts and whilst I have found that this appears to be a common issue, I cannot find a definitive answer or workaround.
The only solution I have come up with is to have 2 flows, one for additions and one for modifications. I've tested the one for additions and this works correctly - runs only once. I need to test the latter but thought I would reach out and see if this is a known issue or if there is a proper resolve.
I read something about a Callback Registration table and tried that solution which was deleting the duplicate row in that table but to no avail and it just ended up creating another row.
Do I just need to log this with Microsoft?
Thank you in anticipation.

Report
All responses (
Answers (