You’re offline. This is a read only version of the page.
Background
I’m currently working on integrating my API with Copilot Studio, but I am facing a challenge related to the size of the responses.
My API returns a relatively large dataset: the uncompressed response size is about 800KB, however when compressed it is about 30KB.
The problem
Copilot Studio seems to limit the response size (50K?) which is why I added "Accept-Encoding: gzip, inflate" to the request's header.
When triggering the HTTP request node, I'm getting the following error:
Error Message: HTTP action with id 'Ku8yD8' got an invalid response body back from the endpoint Error Code: HttpRequestInvalidResponseBody Conversation Id: ddbaa25c-6756-432a-bf90-a391d0bc3641 Time (UTC): 2025-01-02T17:14:22.863Z
When I omit the accept-Encoding header, I'm getting the following error:
Error Message: The output returned from the connector was too large to be handled by the agent. Try reducing its size by utilizing available connector filters or by limiting the number of configured action outputs. Error Code: AsyncResponsePayloadTooLarge Conversation Id: e63a0b76-4d81-47e4-a889-143fb1153b3e Time (UTC): 2025-01-02T17:59:10.460Z
What do I need to resolve this?
I either need a way to set CoPilot Studio to accept a larger responses, or to make it support gzipped response, like most HTTP clients do, or, maybe there is another path.
Limiting the response size to such a small limit while not supporting gzip doesn't make sense for a real world application and I'm hoping there is a solution out there.
Clarification
1. The same integration works fine with my servers when the response is relatively small.
2. Significantly limiting my own server responses size to 50K is not a good option for me.
Any advice or recommendations on how to proceed with this integration would be greatly appreciated!
Thanks in advance!
Share
Report
All responses (
Answers (
1,539
