Showing results for 
Search instead for 
Did you mean: 
Advocate II
Advocate II

Flow is starting multiple times?

I have a flow which is supposed to start whenever there is a new or modified item in a list. For some reason, the flow sometimes runs two, three or even four times. The flow is creating new users in our O365 tenant. Whenever a user already exists, the flow should only update and not create the user (e.g. location of the user has changed). When flows are starting multiple times the condition whether its a new or existing user can't be triggered as they're running simultaneously, causing multiple account creation.


You can see there is nothing special about when the flow is supposed to start.




but a lot of instances:




Anyone experienced this issue before?

New Member

Also Facing the same issue 😞

Hello Team,


Can you provide some additional details as to what are you currently implementing in the flow ?

New Member

I am getting the same issue with "When an email is flagged" as trigger. Any ideas of a resolution? This topic started on 2018. 

Not applicable

I am facing the same issue but with the 'When a new event is created (V3) trigger'. I have multiple other flows that do the same proces but with another outlook agenda. They don't face this issue. Very peculiar.


Helper I
Helper I

Also having this problem.  

Advocate V
Advocate V

I am also having this same issue....a nightmare.

I was able to resolve by filtering the trigger to only 1 column.  

Regular Visitor

I am getting this behavior when using "when file is created" trigger. Today I had two files created in a folder which each triggered the flow 3 times. 


I want to avoid adding a concurrency control as this automation should be processing invoices as they come in, and with approvals and other tasks, enabling concurrency control is going to create a bottle neck.


Why would a flow be triggered multiple times if a file is only created once? 

Leemax, This fixed our issue. Click the burger button on the first step of the flow and select "Settings".

Scroll down and "Concurrency Control". Change Degree of Parallelism to 1.

Frequent Visitor

Also having this issue.  Any resolution?  Using the "When a row is added, modified or deleted" trigger; single lookup column noted in 'Select Columns'.

Changing any field triggers multiple runs (even though they are not the field listed in Select Columns).

Thanks this worked for me too!

Helpful resources

Power Automate News & Announcements

Power Automate News & Announcements

Keep up to date with current events and community announcements in the Power Automate community.

Community Calls Conversations

Community Calls Conversations

A great place where you can stay up to date with community calls and interact with the speakers.

Power Automate Community Blog

Power Automate Community Blog

Check out the latest Community Blog from the community!

Users online (5,608)