I have a table I use to monitor a large number of webhooks. It maxed out at 50,000 events and stopped receiving events. I deleted all rows from the table, but it is still not receiving events. I added a 2nd webhook to the table, and still no events are showing up. So, it appears that when you hit the 50k row limit the table breaks forever?
When a webhook table reaches its capacity limit, it may stop processing new events. Deleting rows doesn't automatically reset this limit. The 50k row limit doesn't permanently break the table, but you might need to create a new webhook table to continue processing. Some things to consider: 1. Check if you're within the rate limits (10 records/second, max burst of 20). 2. Ensure your payloads don't exceed 100KB. If the issue persists, you may need to set up a new webhook table. If you need further assistance, please request to talk to a person in this chat for more detailed troubleshooting.
No, that answer is not satisfying.
It looks like adding a new webhook to the table may be a work around. Still investigating.
Confirmed I had to delete the old webhook. When I looked at the details, it still said there were 50,000 rows associated with the webhook even though I had deleted all of the rows.
Hey Ted, thanks for reaching out. Clay tables do have a 50k row limit, this is something our team is working on increasing. However, we do have a feature that will auto-delete rows in this table so that limit is never met. These are called passthrough, or auto-delete tables as shown here. Let me know if this is something you may be interested in. It's available on Enterprise plans. :)
This thread was picked up by our in-app web widget and will no longer sync to Slack. If you are the original poster, you can continue this conversation by logging into https://app.clay.com and clicking "Support" in the sidebar. If you're not the original poster and require help from support, please post in 02 Support.
can you please advise on how to setup a passthrough table?