Skip to main content

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?

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!


Reply