Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Best answer

Quickbase suddenly erroring: Response payload size exceeded maximum allowed payload size"

  • October 10, 2024
  • 2 replies
  • 98 views
S

Is there some kind of new limit on the number of fields in a table and the ability of zapier to load them?

I have 100+ zaps that create records in or update records in a table in a Quickbase app, and suddenly at 1:45PM PST yesterday,  the zap step can no long see or load any of the fields in this table and now all of my zaps that use these actions are erroring out and it’s causing major problems for me.

The step gives this error:
 

This Quickbase step hit an error

Error message: Response payload size exceeded maximum allowed payload size (6291556 bytes).

But when I go in and edit the step,  it shows all of the mapped fields as ‘Extra Fields’ and will no longer load any of the fields in the table.


Everything had been working fine for years in some cases and suddenly the entire thing is stopped.

So far support has been extremely slow and unresponsive.   

Is anyone else noticing any similar issues?   Is this new?

Best answer by SamB

Just following up here to share that the feature request has been closed! 

The ability to limit the fields/size of records returned wasn’t added however, the developers of the Quickbase app have increased the size limit of the default response which should prevent those “Response payload size exceeded maximum allowed payload size (6291556 bytes).” errors going forward. 😁

As these errors have been resolved, I’ll be closing this topic now. If you continue to encounter any issues, please post a new topic in the Community here or contact Support directly to let us know.

Happy Zapping! ⚡

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

2 replies

SamB
Community Manager
Forum|alt.badge.img+11
  • SamBCommunity Manager
  • Community Manager
  • 9751 replies
  • October 11, 2024

Hi @SSNJeff, welcome to the Community! 🎉

I’m so sorry to hear that you’re suddenly getting these errors with all your Quickbase Zaps. I can see in the ticket you’ve got open with our Support Team that they’ve since added you to a feature request for the ability to limit the fields/size of records returned after creating/updating a record. Which should help reduce the response size and avoid that error in future. We can’t make any promises as to when the developers of the Quickbase app on Zapier will be able to add that functionality but we’ll be in touch to keep you in the loop on progress! 🙂

Really wish we had a more immediate fix or workaround to share. If there’s anything else we can help with in the meantime do let us know.
 

For anyone that comes across this and wants to be added to that feature request just send us a reply here and we’ll get you added!

SamB
Community Manager
Forum|alt.badge.img+11
  • SamBCommunity Manager
  • Community Manager
  • 9751 replies
  • Answer
  • April 23, 2025

Just following up here to share that the feature request has been closed! 

The ability to limit the fields/size of records returned wasn’t added however, the developers of the Quickbase app have increased the size limit of the default response which should prevent those “Response payload size exceeded maximum allowed payload size (6291556 bytes).” errors going forward. 😁

As these errors have been resolved, I’ll be closing this topic now. If you continue to encounter any issues, please post a new topic in the Community here or contact Support directly to let us know.

Happy Zapping! ⚡

Terms & ConditionsAccessibility statement