Flow triggering twice after one submission

[jnakhle]

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? 

[trice602]

Hi @jnakhle ,

Can you include your expanded flow here please?  There's no way to determine a root cause by just looking at the run history.

[jnakhle]

The user selects from the list, fills in the necessary info and an email gets sent with that info filled into the body. The To: email is hard coded into the flow. I also have two connections on this flow. One for Forms and one for microsoft outlook because I thought that was necessary. Could the issue be because of the two connections?   

[trice602]

Hi @jnakhle ,

Thanks for sharing.  No, the connections to Forms and Outlook are not the issue, and they are required, on the surface the issue is going to be inside your conditions that you have collapsed.  Can you share the last run (flow screenshots) that duplicated please?  

[jnakhle]

Sorry if I have the wrong screenshots here. Is this what you are looking for?

[Nived_Nambiar]

Hi @jnakhle 

Could you show the settings of trigger ?

[trice602]

@jnakhle @Nived_Nambiar ,

Not sure what is inside the parallel actions, but at a quick glance you have two branches that were successful.  What are these? I am trying to understand what the four branches do here?

[jnakhle]

Each branch sends to a different email. The user selects one of the branches and fills in the necessary info and submits the form. I unfortunately am very new to this and did not create the form but am now responsible for learning/fixing. 

[Nived_Nambiar]

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?) 

Thanks & Regards,

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! 🙌

[trice602]

Hi @jnakhle ,

My reply was incorrect here so removed it.  FYI -

[jnakhle]

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? 

[brianxp]

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?

Some facts

1. Multiple flows have the same problem
2. These flows share the same Connection Reference
3. These flows exist in the same solution
4. Running them normally causes them to trigger twice
5. Running them with the Test button causes them to trigger twice
6. They all use a manual trigger
7. There are not any errors
8. They call child flows
9. New flows created do not have this problem (as far as I have tested) but they are simple flows but use the same Connection Reference as the other flows which do have the problem
10. Looking at the Connection Reference details before running the flow, the flow will appear once under "Flows using this connection"
11. Looking at the Connection Reference details after running the flow, the flow appears twice
12. Many of them use a "Respond to PowerApp or Flow" step. However, as indicated below, to test that none of the steps flowing the Manual trigger are causing the issue, I tried adding a Terminate "Successful" step immediate after the trigger and the issue still occurs.
13. The flows exist in both Solution A (Development environment) and Solution B (Production). The fundamental difference is that Solution A flows have been updated to use manual triggers. Solution B uses Recurrence triggers. Solution B flows do not experience this issue.

Things I have tried

Description	Result
Removing the flow from the solution and adding it back in	Same issue
Deleting the manual trigger, replacing it with a different trigger, saving the flow and then changing it back to a manual trigger	Same issue
Creating new connection references and having the flow use that one instead	Same issue
Deleting the old connection reference and creating a new one	Same issue
Terminating the flow with the Terminate action right after the manual trigger	Same issue
Resubmitting a flow that has already ran	Issue does not happen

[brianxp]

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.

[tmd]

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.

[NPPlatform]

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!

[ELAISA12345]

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.