Power Automate

HTTP Requests on 3/6/2026

(1) Share

Report

Posted on by JM-06031936-0

Anyone else having sudden trouble with HTTP requests failing after about a minute today?

Categories:

Using connectors

I have the same question (0)

All responses (7)

Answers (0)

Sort by

David_MA 14,956 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

I have not seen any problems; I use HTTP requests in almost all my flows. Looking at run history for the past hour shows everything is looking good:

If you are still having issues, I would share a screen shot of the configuration of the HTTP action and redact any sensitive information. Also include any error information you get it the failed run. Otherwise, about the only thing we can tell you is I am having the same issue, or in my case, everything is working A-OK.

Was this reply helpful? Yes No
JM-06031936-0 7 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi David,

I am getting the error listed below. Interestingly, I am getting this regardless of what URI or parameters I use -

Action 'HTTP' failed: Http request failed as there is an error: 'The server returned status code '504' when status code '101' was expected.

Was this reply helpful? Yes No
JS-07032205-0 4 on at

Like
a
(0)

Report
Copy link

Link copied!

I am having the same issue as you. I have a couple different flows that are sending HTTP requests and they all started failing a the same time. It can't be the remote host since the flows are using different APIs...

I am going to attach a screenshot below. Something broke between 9 and 10am PST on March 6th and now my flows are all timing out with error code 504.

Was this reply helpful? Yes No
AD-08030127-0 2 on at

Like
a
(0)

Report
Copy link

Link copied!

any guidance

getting same error : "The server returned status code '504' when status code '101' was expected."

Was this reply helpful? Yes No
Suggested answer

David_MA 14,956 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Are the flows that are failing using the action or calling a flow with the trigger action When an HTTP request is received?

If so, open the flow with this trigger and click on the trigger. Check if there is a warning message that the URL needs to be updated. If so, you need to copy the HTTP POST URL and update any calling workflows with the new URL. This was deprecated last August and took effect in November, so your flows should have been failing before now if this were the issue.

Knock on wood I am still not encountering this issue in any of my flows. Therefore, it would be best to post a screen shot of the flow that is failing and which HTTP request action is being used as there are more than one HTTP request action to choose from. This will help narrow down the issue. Also show how the action is configured and any error message that is returned. Otherwise, you're not likely to get much assistance in solving the problem.

Was this reply helpful? Yes No
JM-06031936-0 7 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi everyone,

The issue was resolved automatically for me. At the end of the day on Friday, I was able to prove that the issue was only present in our default Power Platform environment. If we moved the flow to another environment the issue did not exist. I didn't have a chance to move over my flows on Friday, but when I logged on this morning the issue was gone in our default environment.

Hope the same for anyone else having this issue!

Was this reply helpful? Yes No
JS-07032205-0 4 on at

Like
a
(0)

Report
Copy link

Link copied!

My issue also resolved itself, so I'm guessing it was some sort of Microsoft issue. My flows are back to working normally.

Was this reply helpful? Yes No