Understanding and Fixing API 400 Error: Queue is Full

Aditya K.

·

Clay received a 400 error from the API with Content: Queue is full.

What is this error about and how to fix this error.

7 comments

· Sorted by Oldest

Channeled
APP
·
·
The "400 error: Queue is full" from the Clay API likely indicates that you've exceeded the rate limits for webhooks in your workspace. Our system can process up to 10 records per second, with a maximum burst capacity of 20 records per workspace. To fix this error: 1. Reduce the frequency of your API calls 2. Batch your requests to stay within the limits 3. If you have multiple webhook sources, consider adjusting their configurations If you need further assistance, please request human help by clicking on "Talk to a person" in this chat.
Source: Import Data to Clay Using Webhooks
Daniela D.
·
·
Hey there! Thanks for reaching out. Happy to help✨. Could you share your table url? We'll check this.
Channeled
APP
·
·
Aditya K.
·
·
Clay | Visitor Oil & Gas check at the last column when I push data to hubspot it shows an error
Daniela D.
·
·
Thanks for sharing! The error message indicates that the Make.com webhook queue was at capacity and could not process the request. This is typically related to the rate limits imposed by make.com. It should process requests now if you re-run the cells, but we recommend reviewing those limits to better manage the number of requests sent within a specific time. The HTTP API column has a custom rate limit that can be configured as well. You can set a minimum limit of 5 requests/second for processing requests.
(56 kB)
Aditya K.
·
·
I am looking to find personal contacts of peron so which tool or waterfall should I use.
Daniel K.
·
·
;Hey there, thanks for reaching out! ☺️You can use the personal email waterfall:
(158 kB)
If there's anything else I can assist you with, please let me know! 😊 Have a great Wednesday, Daniel

Channeled
APP
·
·
The "400 error: Queue is full" from the Clay API likely indicates that you've exceeded the rate limits for webhooks in your workspace. Our system can process up to 10 records per second, with a maximum burst capacity of 20 records per workspace. To fix this error: 1. Reduce the frequency of your API calls 2. Batch your requests to stay within the limits 3. If you have multiple webhook sources, consider adjusting their configurations If you need further assistance, please request human help by clicking on "Talk to a person" in this chat.
Source: Import Data to Clay Using Webhooks
Daniela D.
·
·
Hey there! Thanks for reaching out. Happy to help✨. Could you share your table url? We'll check this.
Channeled
APP
·
·
Aditya K.
·
·
Clay | Visitor Oil & Gas check at the last column when I push data to hubspot it shows an error
Daniela D.
·
·
Thanks for sharing! The error message indicates that the Make.com webhook queue was at capacity and could not process the request. This is typically related to the rate limits imposed by make.com. It should process requests now if you re-run the cells, but we recommend reviewing those limits to better manage the number of requests sent within a specific time. The HTTP API column has a custom rate limit that can be configured as well. You can set a minimum limit of 5 requests/second for processing requests.
(56 kB)
Aditya K.
·
·
I am looking to find personal contacts of peron so which tool or waterfall should I use.
Daniel K.
·
·
;Hey there, thanks for reaching out! ☺️You can use the personal email waterfall:
(158 kB)
If there's anything else I can assist you with, please let me know! 😊 Have a great Wednesday, Daniel