Announcements
We are observing unexpected behavior in the HTTP action in Power Automate since about 1 week. All flows worked for over a year+ - some have been created in the past 3 months others are untouched for a year or more.
Our API returns:
Content-Encoding: gzip Content-Type: application/json
The HTTP action setting “Automatic decompression” is turned ON. However, instead of returning parsed JSON, Power Automate returns:
{ "$content-encoding": "gzip", "$content-type": "application/json; charset=UTF-8", "$content": "H4sIAAAAA..." }
Toggling “Automatic decompression” ON/OFF has no effect
The behavior is reproducible across flows
The same endpoint works normally in Postman and curl
This setup worked previously in production for months
Questions:
Has there been a recent change in the HTTP connector behavior?
Under which exact conditions does “Automatic decompression” apply?
Currently the only workaround is to manually base64-decode + gunzip (e.g., via Azure Function), which significantly complicates flows.
Any clarification would be appreciated.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Jump in, show your community spirit, and win prizes!
Expanding mentorship, skilling, and AI innovation
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Valantis 377
11manish 279
David_MA 234 Super User 2026 Season 1