Avoid a conflict when 2 Flows run with the same trigger

(0) Share

Report

Posted on by webbrewer

336

I have 2 Flows for the same library and both are triggered by "when an item is created or modified". One sends an email, one sends a push notification to a mobile app and both change a boolean field to prevent looping. When they run together, there's a risk of a conflict due to them both changing fields simultaneously. I can't combine them because the email has to be sent from an Azure id that currently doesn't have access to the premium http action required to send the push notification - so I'm concerned that 2 different users making changes to a page property at the same time could result in a conflict.

Is the best option to just put a delay after the trigger in one of them, and hope they don't clash? Or is there a better way?

I have the same question (0)

All responses (1)

Answers (0)

Barret 652 Most Valuable Professional on at

Like (0)

Report

Re: Avoid a conflict when 2 Flows run with the same trigger

Yeah, if you can't combine the flows to run from the same user, then I would add a delay action right after your trigger in one of the flows.

Was this reply helpful? Yes No