For some reason my flow gets trigger twice at the same time after just one submission. I am not referencing any other flows. What could I do to fix this? Is there a trigger condition I could set to prevent the second trigger?
I was facing the same issue and I read dozens of posts like this. What works for me was copy the flow, turn off the old flow and when I run the copied flow, It not runs twice anymore.
I had the same problem of flows triggering twice and your setup (adding a terminate after the Respond to Powerapps-step) seems to work for me too. Thanks for sharing!
I also have this issue and it began Sept 29, 2023. I can only speculate there is an issue on the backend of Power Automate as I have used these automations for three years now and this is the first time it has happened. I do not have the "Respond to PowerApp or Flow" step in any of my automations.
Edit: Apparently the conditional way did not work as I thought. However, unlike before, having the "Respond to PowerApp or flow" step added normally does not timeout anymore, even when triggered directly and not from another flow or PowerApp. The below setup seems to work okay now too.
-------------------------
Just an update to the above, at least on my end.
I'm not sure exactly why but it seems like having the "Respond to PowerApp or Flow" present in the flow, causes it to trigger twice for some reason regardless of where that step is placed in the flow.
Even if I terminate the flow before it reaches that step, it'll still trigger twice.
Originally I had a set up like the following:
If the flow was triggered directly on Power Automate, the "Respond to a PowerApp or flow" step would time out and I would set Terminate to run after if the previous Scope had a time out. However, if it was triggered from PowerApps or another flow, it would be fine.
Again, even though the flow does not reach this step, it'll trigger twice.
Taking a different approach, I have somehow been able to prevent this issue. I have a Yes/No flag set on the Manual trigger. If true, it'll try to do the "Respond to a PowerApp or flow" step.
I still don't quite understand why this works since the previous version of the flow did not even reach the Try scope. Additionally, this does not explain why resubmitting the flow from the flow run history does not reproduce the issue. Perhaps resubmitting is treated differently than executing/testing?
Perhaps by simply existing in the flow, the flow is expecting some sort of callback or something and, since that doesn't happen, it immediate runs twice but does not expect a callback if being resubmitted? It's a big mystery to me.
Anyways, a day has passed since I tried my solution so I'll double check that it is still working. If not, I'll follow up.
I'm actually running into a very similar issue so I thought I'd share. I've submitted two tickets to Microsoft Power Platform support but neither has been responded to. The first ticket was submitted 2 weeks ago but I am not sure how long the response time is typically.
Not sure if the below info helps but maybe there are some commonalities?
Here is a screenshot of what the user sees. They select an option, the user fills in information, then submits the form that then gets emailed to a certain group of people. However I just noticed something - there are 5 options here but only 4 branches? I sent a test to the one branch not in the form I sent screenshots to and the flow ran successfully. Does that mean there must be another flow in use?
Hi @jnakhle
So in each branch you are sending email to person to fill form which they need to submit (is it the same form?)
Nived N 🚀
LinkedIn: Nived N's LinkedIn
YouTube: Nived N's YouTube Channel
🔍 Found my answer helpful? Please consider marking it as the solution!
Your appreciation keeps me motivated. Thank you! 🙌
Tomac
986
Moderator
stampcoin
699
Super User 2025 Season 2
Riyaz_riz11
577
Super User 2025 Season 2