Power Automate HTTP GET to sas_uri returning 504 — "server returned 504 when 101 was expected" — started after March 5 outage

Anne Dicker

All of our Power Automate flows using the RENXT Query connector stopped working on March 7. The query job starts and completes successfully, a valid sas_uri is returned, but the HTTP GET to download the blob fails every time with:

"The server returned status code '504' when status code '101' was expected. (nsa-pusa01.app.blackbaud.net:443)"

The sas_uri is valid — it downloads correctly in a browser. The failure is specifically Power Automate's HTTP connector being refused when it attempts a WebSocket upgrade (101) against nsa-pusa01.app.blackbaud.net.

Nothing changed on our end — no flow edits, no policy changes. We've tried Connection: close, Upgrade: "", chunked vs non-chunked transfer, Inline vs Attachment content_disposition. All fail the same way.

Is anyone else seeing this? Did something change on the blob storage infrastructure after the RE NXT outage last Monday?

Alex Wong

i have no problem with any of my power automate that uses Query API and then download using HTTP action.

This issue was back on Feb 10, so not sure why you are seeing this now and if it's related, but something to check first.

Anne Dicker

Thank you. That worked.