When HTTP Request is Received - Triggers Multiple Times

[jennratten]

Hello- I have a flow that utilizes the trigger 'When a HTTP Request is Received'.  I have placed the URL in an Excel file as a hyperlink.  The Excel file is saved in a Teams channel files (and therefore Sharepoint). I also have a shortcut to the directory mapped to my desktop OneDrive. The flow works just fine, however, when the link is clicked from the file in Sharepoint, the flow triggers once (correct), but if clicked from Teams it runs twice, and if clicked from Excel desktop, it runs three times.  Is there a way to configure it to only run one time regardless of the source from which it is triggered?

[aerojean]

I came here looking for exactly this. I'm sending a single request to the "When HTTP Request Is Received" trigger and it's running twice at the same time, one with the expected outputs from the request's body and the other with no outputs. I have yet to find a solution. This definitely looks like a bug.

[Kaizer]

Hi im having the same issue. Any solutions?

[aerojean]

Not yet. I opened a ticket with Microsoft Power Automate Support and they're looking into it. I will update this post once I get a definitive response.

[aerojean]

Microsoft Support responded to me by suggesting a workaround using trigger conditions. Basically since what was happening to me was that the double trigger one had output parameters and the other didn't, I put a trigger condition saying to not run unless there is a trigger body. The condition I used is this one: @not(empty(triggerBody())). Another condition that also worked was this one: @not(equals(triggerBody(), null)).

So far it has worked in preventing the "fake" second trigger to run. They told me that they have raised this issue with the appropriate team to work on a fix but these bug trackers are not public so I guess we'll never know if it ever gets fixed.

This is still just a workaround and the trigger isn't reliable if it keeps behaving unpredictably but it's what I have for now.

[Kaizer]

Hi Can you share your flow with regards to this trigger. Having trouble trying to make it work with mine.

[aerojean]

Hello Kaizer

 

So far it's been working well with the below trigger condition:

 

This has worked for me because in my case the trigger got activated twice, one with the regular expected inputs and the other without any inputs (empty body). This trigger condition makes it so that only the valid trigger runs, and the other duplicate and invalid trigger does not run. You can access these trigger conditions in the triggers settings:

Is this similar to what you're experiencing? Hope it helps.

[Kaizer]

Thanks i just tried that now. Now the flow doesnt run at all. Stops it from triggering at all. My problem was similar to yours where if using excel desktop and inserting the "get" link into a button or image to to trigger the flow it ends up doing it twice which i didnt understand. Dont understand why your solution isnt working for me.

[Kaizer]

in addition to my above message as you can see from the image it runs it twice from excel desktop. one second after.

[aerojean]

If you're activating the flow with just a URL link and no additional parameters, which is what I think your case is, then yes the trigger condition I mentioned will apply to all of your requests and none of them will end up running because of it. I'm guessing Excel tries to open the link through the default browser. Things you could check:

1. Set up a different default browser. Does this behavior happen with different browsers set as default? Maybe it's a browser specific behavior that's sending two requests instead of one.
2. Does the double trigger happen if you copy the link and manually paste it on the address bar of a browser window instead of letting Excel open the browser and link for you?

The truth is even if everything in your computer is working as it should this trigger doesn't behave 100% as advertised and it's buggy. In my case I was strictly doing a single request and it still triggered twice.

[kaizechowdhury]

Thanks for the quick replies. Yes on point number 2 when I paste the link directly in browser it runs perfectly and runs once. By default it opens via chrome don't think I can change the default browser. 

How is yours configured? Isn't it similar to mine where you are getting the link from power automate and using it in Excel or teams? 

[aerojean]

In my configuration I'm using the link elsewhere, the original poster was using Excel. In your configuration it then seems like the flow is working correctly and it's the browser and/or the way of opening the link that is sending 2 requests quickly one after the other instead of the trigger responding twice for a single request, which was the problem I was having.

At least we were able to narrow down the problem a bit. I'm not sure how to resolve it other than trying different browsers or ways to open the link that don't result in sending the request twice.

[Aysan]

Hi @jennratten 

Would you please help me figure out how you could get information about the excel file? I am working on a scenario close to yours, I am triggering the flow from the excel file using a button, just trying the get the file path/name in the flow 

[JM8221]

Hi all,

I hope that my suggestion would be helpful for you.

------------------------------------------------

I didn't use a button linked to the trigger url because of the same issue with you.

I used a macro button and the VBA code as follows.

Sub openurl()
Shell "rundll32.exe url.dll,FileProtocolHandler " & "input your Trigger URL", vbNormalFocus
End Sub

and then you will not see the trigger multiple times issue anymore.

Good luck.

[Bruno_Andrade]

Hi!

I'm still having this issue with the HTTP trigger.
Was anyone able to bypass this issue without using macros?

The empty body solution isn't working as the output just have headers 😕

Thanks!

[Jaco_Campher]

Hi

Was having a similar problem, just not from excel. Was calling from another workflow and also getting duplicate runs, but think I found the problem.

This is from the first (Correct) run:

This is for the second (Duplicate) run:

At least in our case it looks to be the keep alive that is the problem.

Adding this trigger condition solved it:

@not(equals(triggerOutputs()?['headers']?['Connection'], 'Keep-Alive'))

UPDATE:

Just found out that when you call from a flow that is not in a solution, the keep alive is also there. So this is still not a solution.

[Michel21]

It worked for me when i added the trigger conditions 

@not(equals(triggerOutputs()?['headers']?['Connection'], 'Keep-Alive'))

@not(equals(triggerOutputs()?['headers']?['Connection'], 'keep-alive'))

for some reason one request had it writen with upper case K and A and the other with lower case a and k

[Jan_Ur]

I used this trigger condition

@contains(triggerOutputs()?['headers'], 'sec-ch-ua')