Flow triggered multiple times

[C-Jac]

I have an issue where my flow triggers multiple times, where it should only have been triggered once. This error started a few days ago. 

It is a manually triggered flow, so it cannot have anything to do with performing the same action multiple times. 

When I click run the flow, it 'hangs', and then it times out and gives me below error: 

And after exiting the run, and refreshing all the runs, the flow has been triggered not only once, but 3 times. It is 3 times every time, like below screenshot: 

I know that for some of the commands you can have a try policy, but I can't find this setting for the flow itself. It is a flow that takes 10-26 min to run. 

Does anyone know how I can fix this? 

[Nico_0710]

Hey,

Is the problem only since today and did the flow work as desired before?
Sounds strange, but maybe restart the browser, I had the same problem some time ago.
If that doesn't help, you can consider using a different trigger, if one can be helpful for you.

If my solution helped, you can mark the post as a solution to make it easier for other users to find.

Greetings Nico

[C-Jac]

Hi Nico, 

This started happening a few days ago, and the flow worked as normal before that. It is a manual trigger, so when I just click run it does this. I also have the ability to trigger it from a parent flow, but here I get the same result. No matter what I try, the flow still triggers multiple tries 😞 

[Nico_0710]

Hey C-Jac,

I haven't heard that yet. If you want your flow to always trigger at a certain time or at regular intervals, you could try setting the manual trigger to a certain time. This could help to trigger it only once at a time.
Hope this helps.

Greetings Nico

[C-Jac]

Hi Nico, this is a flow that needs to run on a request basis, so we trigger it when we need it, and not at a specific time every day. The issue continues to exist, where it triggers 3 times instead of just the 1. I have raised an issue with Microsoft and I am waiting for them to answer. This is the only flow where it happens 😞 

[Nico_0710]

Do you mind sending me your full flow ? Maybe then I will get where and why the flow is triggered that many times.

[erikmf12]

Did you ever figure this out? I'm having the same issue with 3 runs being started after a manual trigger. 

[doschtert]

Hi @C-Jac ,

did you get any response from Microsoft? 
I've got the same problem, I have manual flows that get triggered multiple times and they are also attached to parent flows. 

Let me know, if you got a solution on this, would be really interesting to know! 🙂

Thanks!

[Jaasha]

Hi @C-Jac 

Did this happen every time when you triggered the flow or just every now and then? I have a similar issue, where I have a manually triggered flow and about once in every 100 runs the flow triggers and runs three times from one call. Did you ever receive any response from Microsoft?

[doschtert]

Hi everybody,

I had the same problem for quite some time and funny enough, I might have found the solution just 2-3 days ago. 

I found out, that when a child flow gets triggered by the parent flow and it didn't work for some reason, it will retrigger it again and again and again... and you know the drill.. 😀

So what I did was checking the Run history of the parent flow and filtered it by flows "running". I found a few and aborted them all. 
Since then (the last 2-3 days basically) I did not get any new runs from the child flows. 

I can't tell whether this is actually the solution, but check it out, for me at least it worked until now. 😉

[C-Jac · Accepted solution]

I found out that this was because my flow was triggered by a parent flow, and I had not added a response to an app or flow inside my flow. This flow needed to be triggered either manually or by another flow, so I added a variable to indicate whether it was triggered by a flow or manually, and if it was triggered by a flow (parent flow) an if condition would then trigger the response sent to a power app 🙂