<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.appian.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Integration component allows only 5 MB response</title><link>https://community.appian.com/discussions/f/integrations/14568/integration-component-allows-only-5-mb-response</link><description>Hello, 
 
 I&amp;#39;m calling REST webservice in integration component which returns more than 40k records which goes beyond 15 MB. 
 In this case integration component fails saying: &amp;quot;Unable to process response body - The response body was greater than 5 MB</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Integration component allows only 5 MB response</title><link>https://community.appian.com/thread/65314?ContentTypeID=1</link><pubDate>Thu, 21 Mar 2019 20:58:47 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:8b121d68-647e-44fd-9328-47e54350dc29</guid><dc:creator>Tim</dc:creator><description>40k records seems like a sub-optimal design! Most production ready REST services that I&amp;#39;ve used will utilise a $skip query parameter that allows paging of the data. Some such as Microsoft&amp;#39;s graft will even provide the URL for the next fetch in the response. My only recommendation would be to speak to the webservice designer and suggest they make it more scalable in the politest way possible.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>