Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Response size too big. Maximum allowed response size: 7340032b

See original GitHub issue

Expected Behavior

Calling client.getEntries should get all of my data.

Actual Behavior

I’m getting this error message Response size too big. Maximum allowed response size: 7340032b.

Possible Solution

Here’s my config when calling the getEntries function await client.getEntries({content_type: 'xxxx', include: 3}); I know that the include:3 causes it to make the response size too big but we have some functions where we need our data all at once. I could have set a first or skip here but it is not an option right now

It would be nice if there’s a way to override the maximum allowed response size

Steps to Reproduce

Just have a large set of data without any filtering or pagination.


When we were starting with Contentful 6 months ago, we only had a few data so this was not an issue. We’re using Hugo to generate our web pages and we generate the md and json files using Contentful.


  • Language Version: v11.4.0
  • Package Manager Version: 6.9.0
  • Operating System: Ubuntu 18
  • Package Version: ^7.9.1
  • Which API are you using?: Delivery

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:5
  • Comments:8 (1 by maintainers)

github_iconTop GitHub Comments

brijmcqcommented, Aug 7, 2019

thanks @Khaledgarbaya . My workaround is something like this

  const data1 = await client.getEntries({ content_type: 'xxxx', include: 3, limit: 10 });
  const data2 = await client.getEntries({ content_type: 'xxxx', include: 3, skip: 10 });
  const allData = {};
  allData.items = [...data1.items, ...data2.items];
jwugitcommented, Mar 11, 2022

for anyone looking into this in the future, it might be due to contentful technical limits. image

Read more comments on GitHub >

github_iconTop Results From Across the Web

Response size too big - APIs - Contentful Community
Getting a “Response size too big” error when trying to fetch content entries because the limit setting gets applied to all attributes on...
Read more >
Contentful export tool - npm
Error: 400 - Bad Request - Response size too big. Contentful response sizes are limited (find more info in our technical limit docs)....
Read more >
AWS Lambda - Body Size is Too Large Error ... - Stack Overflow
Error Message returned by lambda function build with python 3.7: Response payload size (8198440 bytes) exceeded maximum allowed payload size ( ...
Read more >
Technical Limits - Contentful
We enforce technical limits to ensure the shared-service infrastructure ... Asset size, including images larger than the image size limit, 50, MB per...
Read more >
contentful - Bountysource
Linked entries - Response size too big. Maximum allowed response size: 7340032b. $ 0. Created 2 years ago in contentful/ with 0 comments....
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found