Power Automate HTTP action fails with "Error while copying content to a stream"

(1) Share

Report

Posted on by DK-04121105-0

We have a flow configured with the "When Power Apps calls a flow (V2)" trigger, which sends a POST request to an external service using the HTTP action.

The POST request is sent to external service whose purpose is to execute custom queries against a PostgreSQL database and return the results back to Power Automate, which then passes them to the Power Apps application. When using the HTTP action in Power Automate, the following error is returned in response to the POST request:

BadRequest
Http request failed as there is an error:
'Error while copying content to a stream.'

The request completes successfully when the response contains a very small dataset (approximately 15 records). However, the error occurs when the response contains a larger number of records.

We have been using this approach successfully for more than a year, and this issue only started occurring today.

Categories:

General topics

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

11manish 3,333 on at

Like
a
(0)

Report
Copy link

Link copied!
Since:

The solution worked for over a year.

Small datasets still work.

Large datasets suddenly fail.

The most likely causes are:

Response payload size has increased significantly (most likely).

Malformed/truncated JSON in one of the returned records.

Recent change in the external API or response encoding/compression.

Temporary issue/regression with the Power Automate HTTP connector.

I would start by comparing a successful response and a failing response in Postman (size, headers, and JSON validity). That comparison usually identifies the root cause very quickly.

Was this reply helpful? Yes No
Suggested answer

Haque 3,653 on at

Like
a
(0)

Report
Copy link

Link copied!
Hi @DK-04121105-0,

We have a proven clue "the error occurs when the response contains a larger number of records." So, This error most commonly indicates that the HTTP network connection broke while the payload was actively transferring, or the payload size exceeded the platform's processing limits. Because it failed midway through streaming the data, the target server or application rejected the request as a BadRequest.

Try turning off "Automatic decompression" in the HTTP action settings if it is on already.

Optimize or paginate your query to reduce response size. Check if the API supports pagination by returning a next page URL or token (e.g., @odata.nextLink or a nextPageToken).

Verify headers and content types are correctly set.

Test the API response in Postman and compare with Power Automate.

One more point, we can do a filter early approach: let's shorten the uery boundaries. For instance, instead of pulling a month of log data, apply a tighter filter to pull only 1–7 days for example. Also, Run the Query in SQL and see if data returned by the SQL query is too large. Try reducing the dataset or applying filters as mentioned earlier.

Referenfces:

Time out handling

I am sure some clues I tried to give. If these clues help to resolve the issue brought you by here, please don't forget to check the box Does this answer your question? At the same time, I am pretty sure you have liked the response!

Was this reply helpful? Yes No