Sorry about the ChatGPTing of the issues, but i noticed that since microsoft imposed movingto the new URL all my flow that have queries parameters passed in the URL are now broken because the queries are no longer extract from the queries and made available.
Am I the only one experiencing this issue?
Here is what I plan to report to microsoft when i figure out where i should do so. (by the way anyone know where to do so?):
================
After Microsoft switched Power Automate flows to the new HTTP Request Trigger URL format (August 2025 migration), the queries object in the trigger output is no longer populated.
Previously, when calling a flow like:
https:
I could reliably access query parameters with:
triggerOutputs()?['queries']?['param1']
or
triggerOutputs()?['queries']
Since migrating to the new URL format:
https:
the flow still triggers, but the queries object is missing entirely from triggerOutputs().
Repro Steps
-
Create a flow with a “When an HTTP request is received” trigger.
-
Call the new-style endpoint with query parameters:
-
Inspect the trigger output JSON in run history.
Expected Behavior
triggerOutputs()?['queries'] should contain a dictionary of query parameters, e.g.:
"queries": {
"param1": "abc",
"param2": "def"
}
Actual Behavior
No queries object is present in triggerOutputs().
Only headers and body are returned.
Sample (anonymized) run history excerpt:
Notice: queries is missing, but the x-ms-original-url have the query parameters
Workarounds Tried
-
Extracting query string from
triggerOutputs()?['headers']?['x-ms-original-url']
and parsing manually with uriQuery().
-
Moving parameters into the request body (works, but not backward compatible).
-
Using relative path parameters (possible, but requires client change).
Impact
Request
-
Please confirm if this is an intentional deprecation or a bug.
-
If intentional, documentation should be updated and guidance provided on migrating.
-
If a bug, please restore the queries object in the trigger output.
