Response Body Size Limit

In Appian, you cannot increase the response-body size limit for an Integration object. The platform itself enforces that limit to protect performance and memory usage, and there’s no system property or support setting that can override it.

Typical limits

• Appian Cloud integrations have a maximum response size of 10 MB (for HTTP integrations) as of the current platform versions.
• If the remote service returns more than that, Appian will stop reading and raise the “response body size limit exceeded” error you’re seeing.

Practical Workarounds

• Ask the upstream API to paginate or stream results (e.g., include ?limit/?offset parameters or similar).
• Provide compressed data (e.g., gzip) if the service supports it—Appian automatically decompresses gzip/deflate.
• Use multiple Integration calls in a process model or expression rule to pull smaller pieces (pages) and merge them in Appian.
• If the payload is truly large (e.g., big files), have the external system place it in a file/object store (S3, Azure Blob, etc.) and return only a signed URL.
• Use a Document Download (e.g., Appian’s a!documentDownloadLink()) or a Connected System for S3/SharePoint to fetch the file directly.

We have used many of the workarounds mentioned above in some of our previous clients. We have to basically understand that we don't need the whole output, but if you don't have any control, it's best to store it into a file and later retrieve it.

How can I utilize a PM to break up the calls?

How can I utilize a PM to break up the calls?