Issue with the Flow trigger "When an HTTP request is received"

Question

Hi,

I'm having an issue with flows that use "When an HTTP request is received" as the trigger. Six days ago, all of these flows were working, but now none of them are functioning.

Even though the configuration remains the same, an error is being thrown. The trigger is set to the GET method, which should extract two dynamic variables from the URL (created in another flow:) using triggerOutputs()['queries'] — this used to work, but now it doesn't capture anything from the URL.

Flow configuration (with this trigger):

Error details:

I’d appreciate urgent support on this issue and information on whether there was any update to Edge that could have caused this (although it doesn’t work in other browsers either), or to Power Automate.

Answer 1

Hi,

Thank you very much for the information. I’m looking forward to updates on this topic in this post.

One thing I’ve noticed — the triggers mentioned seem to work flawlessly on the old URLs, which are supposed to stop working on November 30th this year. Could you please confirm this for me? That the triggers are working and will continue to work on the old URLs until November 30th?

Due to the large number of them, I’m unable to test each one individually.

Best regards and have a great day,

Agata

Answer 2

Hi,

Thank you very much for your response. Unfortunately, this is a significant change that wasn’t previously communicated and has caused many flows to stop working correctly.

Can we expect this bug to be fixed in an upcoming update? It’s a major change and unfortunately breaks the intended functionality of the trigger in Power Automate.

Additionally, is there any alternative solution that could replicate the behavior of this trigger? The idea is to automatically create a button in a specific SharePoint folder (upon receiving a response from Forms), which, when clicked, would trigger a second flow. I was previously doing this using the HTTP flow and generating a URL element.

I’d appreciate your support, as this issue is urgent and I need a workaround or temporary solution — ideally, a fix that restores the previous behavior before the update.

Have a nice day :)

Answer 3

Hi Agata F, 

Thank you for posting your question in the Microsoft Q&A forum.

Based on your description and recent updates I've received, it appears the issue you're experiencing may be related to a change in the URL format used by the "When an HTTP request is received" trigger, which is no longer accepted by SharePoint site scripts. Microsoft has acknowledged receiving reports of this issue, and it is currently under investigation. 

I’ve also found several related posts reporting similar behavior. Some of them are listed below: 

• Bug: triggerOutputs()?['queries'] no longer populated with new HTTP Request Trigger URLs 
• Set-SPOSiteScript : Action 1 (triggerFlow) is invalid. Parameter url has an invalid value. 

Unfortunately, at this time, no feasible or officially supported workarounds have been suggested to fully resolve this issue.  

I’m closely following the investigation and will keep you updated as more information becomes available. In the meantime, I recommend monitoring the Power Platform community threads for updates from Microsoft. Hopefully, a more stable and supported solution will be released soon. 

I hope these insights help! If you have any further questions, please feel free to let me know.

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".         

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.