Hey, not sure if this is a known "issue" - but I had a Clay table that was reaching row limits via a webhook so I deleted the rows. the webhook then stopped working. it turns out I had to delete the webhook endpoint entirely including the rows and create a new one. as soon as i did it started pinging again. When deleting a webhook source, it does say tell you how many rows are attached to the webhook but it doesn't say that by not deleting them when deleting the webhook that they still go towards the row limit. the message could be a little clearer so people understand the difference between "keeping a webhook and deleting rows" vs "deleting webhook and rows at the same time" not sure if that makes complete sense but tried to articulate it as best as possible
You're correct about this behavior. Webhook sources have a 50,000 submission limit that persists even after deleting rows. When you delete only the rows but keep the webhook source, those deleted submissions still count toward the 50,000 limit. To reset the counter and continue receiving data, you need to create a new webhook entirely, which is exactly what you discovered. This is the intended behavior - the submission limit tracks total webhook calls received, not current row count. Your feedback about making this clearer in the UI is valuable for improving the user experience.
