QuNect triggers Webhook rate threshold Error 429

Question

I have scheduled QuNect to push a nominal amount of files (~35) into a QuickBase table. A new record is created with the file being loaded into a file attachment field. This works fine but the subsequent Webhook throws an error: "Webhooks are exceeding the rate threshold" (Error 429).
Nonetheless, the Webhook seems to complete successfully; it logs the action (that a new record was added) on a separate table. If the error is inconsequential, can/should I suppress it? If the # of files grows, will the Webhook fail? Does anybody have any thoughts or suggestions here? Thanks!

aryehzelczer6 · Answer

I had the same issue and found the reason was because it was adding into Quickbase row by row. Meaning that it is creating a import from csv for every record which is causing the error. what you need to do is make sure its being added by batch.This way it adds as one&nbsp;ImportFromCSV api call and you shouldn't have this error. Let me know if you have any questions.

michaelbarrow · Answer

How do you tell QuNect to do that? I use it in MS Access and have been anticipating problems like this. Is there some sort of SQL command adjustment that is available or necessary?

richardpfister · Answer

I forgot to follow up here with the resolution to my issue. I opened a ticket with the support team when I didn't hear anything back from the community and here is part of the response I received:

"The error you are seeing means that your webhook is trying to fire too quickly. Webhooks and Quick Base Actions are limited to only firing 10x's a second. With your webhook, it looks like it is trying to push through all 35 records at once, so 35/second. The reason it logs the action as successful is because it will process the first 10, log that action as successful, reach the 10/second limit, and then throw you your 429 error."

My QuNect import is driven by a VB.net script that loops through the files in a folder and Inserts them into QuickBase. My solution was to include a pause after every iteration of the loop so that only one would be loaded per second and thus only one webhook would fire per second.

michaelbarrow · Answer

Sounds like a good work-around. I usually use append queries or update queries to do it directly, and I might need to take the time and overhead to turn it into a form with a looping process with pauses. Thanks for your information!

Forum Discussion

QuNect triggers Webhook rate threshold Error 429

Related Content

Pipeline Not Triggering

429 Error: Webhooks are exceeding the rate threshold

Webhook Pipeline Question

Trigger RULE is there is a change in an attachment field

Carrying the old value of a field into a webhook