Webhook Error: Record Limit Reached Despite 50k Row Capacity

Adil Aijaz · 2025-01-16 20:13:34.226111+00

hey support team., i have a webhook feeding my table. The table has 1k rows right now. I see these errors in our logs: ```{"type":"Forbidden","message":"Record limit reached for webhook","details":null}'``` Looking at docs and support msgs, it's clear that there's a limit of 50k on rows. So why did this webhook stop at 1k? Here's my table:

Webhook Error: Record Limit Reached Despite 50k Row Capacity | Clay

12 comments

· Sorted by Oldest

Channeled
APP
·
·
There are two key limitations that could be causing this issue: 1. Rate limits: Webhooks are limited to processing 10 records per second per workspace, with a maximum burst capacity of 20 records. 2. Passthrough threshold: If you're using a Passthrough table, there's a threshold of 5,000 rows before data starts being transferred to your designated destination. This means data accumulates in the table until this threshold is reached.To resolve this, you could try: ** Batching your webhook requests to stay within the rate limits ** Adjusting the timing between requests * If you need the threshold adjusted, reaching out to support Sources: Import Data to Clay Using Webhooks Configuring your table settings | Documentation | Clay University
Channeled
APP
·
·
Hi Adil Aijaz! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Channeled
APP
·
·
Thank you so much for sharing your feedback Adil Aijaz!
Adil Aijaz
·
·
This isn't a throughout issue. All webhooks are failing for the last two days.
Adil Aijaz
·
·
It's something else
Adil Aijaz
·
·
Can a human please look at this
Channeled
APP
·
·
Based on your table having only 1k rows and seeing the "Record limit reached for webhook" error, this is likely related to webhook rate limits rather than the total row limit. Each workspace is limited to processing 10 records per second, with a maximum burst capacity of 20 records.To resolve this, try: ** Batching your webhook requests to stay within the 10 records/second limit ** Adding delays between webhook requests * If you have multiple active webhooks in your workspace, adjust their timing to avoid overlapping Source: Import Data to Clay Using Webhooks
Channeled
APP
·
·
Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!
Mark (Clay)
·
·
HI Adil. Thanks for getting in touch, and for the table link. I see that your table has de-duplication enabled. As such, new duplicate rows are deleted from the table when they enter. However, those new rows still "count" against the limit for the webwook. (Deleting records does not reset the count.) You'll want to create a new webhook, and in whatever system(s) send data to Clay, update them to send to the new webhook. Could you try that, and let me know how it goes?
Adil Aijaz
·
·
very helpful response. so just so i understand, i just have to update the webhook, not the table? I can also make sure we do deduplication upstream so we don't expire the webhook quickly
Adil Aijaz
·
·
that worked. thank you!
owen (Clay)
·
·
Hey Adil, glad to hear this was helpful! Performing the deduplication upstream would likely alleviate some of the data that is being sent to the webhook thus prolonging the time before hitting the limit. Hope this helps! Feel free to reach out with any other questions or concerns. :)
👍1

Channeled
APP
·
·
There are two key limitations that could be causing this issue: 1. Rate limits: Webhooks are limited to processing 10 records per second per workspace, with a maximum burst capacity of 20 records. 2. Passthrough threshold: If you're using a Passthrough table, there's a threshold of 5,000 rows before data starts being transferred to your designated destination. This means data accumulates in the table until this threshold is reached.To resolve this, you could try: ** Batching your webhook requests to stay within the rate limits ** Adjusting the timing between requests * If you need the threshold adjusted, reaching out to support Sources: Import Data to Clay Using Webhooks Configuring your table settings | Documentation | Clay University
Channeled
APP
·
·
Hi Adil Aijaz! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Channeled
APP
·
·
Thank you so much for sharing your feedback Adil Aijaz!
Adil Aijaz
·
·
This isn't a throughout issue. All webhooks are failing for the last two days.
Adil Aijaz
·
·
It's something else
Adil Aijaz
·
·
Can a human please look at this
Channeled
APP
·
·
Based on your table having only 1k rows and seeing the "Record limit reached for webhook" error, this is likely related to webhook rate limits rather than the total row limit. Each workspace is limited to processing 10 records per second, with a maximum burst capacity of 20 records.To resolve this, try: ** Batching your webhook requests to stay within the 10 records/second limit ** Adding delays between webhook requests * If you have multiple active webhooks in your workspace, adjust their timing to avoid overlapping Source: Import Data to Clay Using Webhooks
Channeled
APP
·
·
Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!
Mark (Clay)
·
·
HI Adil. Thanks for getting in touch, and for the table link. I see that your table has de-duplication enabled. As such, new duplicate rows are deleted from the table when they enter. However, those new rows still "count" against the limit for the webwook. (Deleting records does not reset the count.) You'll want to create a new webhook, and in whatever system(s) send data to Clay, update them to send to the new webhook. Could you try that, and let me know how it goes?
Adil Aijaz
·
·
very helpful response. so just so i understand, i just have to update the webhook, not the table? I can also make sure we do deduplication upstream so we don't expire the webhook quickly
Adil Aijaz
·
·
that worked. thank you!
owen (Clay)
·
·
Hey Adil, glad to hear this was helpful! Performing the deduplication upstream would likely alleviate some of the data that is being sent to the webhook thus prolonging the time before hitting the limit. Hope this helps! Feel free to reach out with any other questions or concerns. :)
👍1