How long does it take for the Clay credit usage page to update?
How long does it take for the Clay credit usage page to update?
How long does it take for the Clay credit usage page to update?
The credit usage page shows your workspace's credit consumption and can be accessed by clicking your account name, going to Settings, then Credit usage in the sidebar. [1] You can filter the data by time period, owner, or specific integrations to track where credits are being spent.
Are you looking for information about how quickly credit usage appears after running enrichments, or are you asking about something else related to the credit usage page updates?
Yup how quickly does credit usage update after running enrichments
Credit usage updates can be delayed up to 30 minutes after running enrichments. [1] This delay allows the full enrichment session to be completed first before reflecting in your credit usage dashboard.
Did that answer your question?
If you need any more help understanding credit usage updates or anything else, I’m here to assist. Would you like to share more about what you’re trying to resolve or understand?
Question on Auto-Delete and webhooks. The docs say that auto-delete deletes just rows in tables and that the webhook has a 50k limit even after the auto delete. So does auto-delete work with webhooks?
I understand this can be a bit confusing, so I’ll connect you with one of our human agents who can clarify how auto-delete works with webhooks.
Clay Support is sharing a file with you.
Our support team has got your message and we'll get back to you soon!
If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!
Hi Nathen - thanks so much for reaching out. To clarify - I believe you're asking for more context on the auto-dedupe feature? The webhook itself has a 50k submission limit that doesn't reset. Auto-dedupe only removes rows from the table, not from the webhook's submission counter. Once a webhook receives 50k total submissions (even if rows were deleted), you'll get "Record limit reached for webhook" error. At that point, you need to create a new webhook.
Hope that clarifies things for you!
I am referring to this page by the way: https://www.clay.com/university/guide/auto-delete
so even if this is enabled on the enterprise plan whenever the webhook reaches 50k submissions you have to make a new table?
I see - thanks for clarifying. You don’t need to make a new table, just a new webhook. With Enterprise auto-delete, your table can stay the same and keep processing unlimited data since rows are deleted after enrichment.
However, the webhook endpoint itself tracks total submissions separately. Once it hits 50k total submissions, it stops accepting new data - even if the table stays under 50k rows. When that happens, you'd have to create a new webhook (new URL) pointing to the same table. The table and its setup remain unchanged; only the webhook needs to be replaced.
We haven't heard back from you here, so we're going to go ahead and close this thread out.
Still need help here? Reply back and someone will jump back in.
Have a question thats not related to this thread? We recommend kicking off a new ticket in the support channel!