Resolving Timed Out Errors with Webhook Row Additions

Rutger B. · 2025-11-25T22:14:01.470Z

Quite frequently I have these Timed Out errors… for a whole bunch of rows that I add via a webhook. is it perhaps because I should rate limit and add them not all at once?

Resolving Timed Out Errors with Webhook Row Additions | Clay

Clay Support
APP
·
·
Yes, you're on the right track! Rate limiting can definitely help with timeout errors when adding webhook data. [1]
The webhook throughput limit is 10 requests per second, so sending data faster than that can cause issues. You should add delays between webhook submissions - at least 100ms between each row.
Also consider processing smaller batches at a time rather than sending everything at once. This helps prevent overwhelming the system and reduces timeout errors.
Clay Support
APP
·
·
Is that what you were looking for?
Clay Support
APP
·
·
If you still need help with managing the timeout errors or rate limiting your webhook requests, I’m here to assist. Would you like to provide more details about what you’re trying to resolve or understand?
Rutger B.
·
·
Manually letting rows run results in same.. Clay bug?
Loading attachments
Clay Support
APP
·
·
The "Sculpting...", "Curating..." etc. messages you're seeing are normal processing statuses, not errors. These indicate the enrichment is actively working through different stages. [1]
The "Run condition not met" messages mean certain rows don't meet the criteria you've set for that column to run.
If you're still seeing issues after manual runs, try clicking into the specific cells showing problems to see more detailed error information. You can also try the "Force" option by clicking the column header and hovering over "Run column" to jumpstart stuck enrichments.
If problems persist, try clearing your browser cache and doing a hard refresh.
Clay Support
APP
·
·
Did that answer your question?
Rutger B.
·
·
55 minutes feels long
Loading attachments
Clay Support
APP
·
·
55 minutes is definitely too long for an enrichment to be loading. Try clicking the column header and selecting "Force" from the Run column dropdown to jumpstart stuck enrichments.
Also do a hard refresh - Ctrl+Shift+R on Windows or Cmd+Shift+R on Mac.
If you're using AI enrichments with a lower API tier, you might need to process smaller batches of around 50 rows at a time.
Clay Support
APP
·
·
Was this useful?
Rutger B.
·
·
I did hard refresh it’s 35 rows I dont want to force run ALL rows just the ones I select
Clay Support
APP
·
·
You can run enrichments on just selected rows using filtered views. Filter your table to show only the rows you want to process, then run the enrichment - you'll only be charged for the rows visible in your filtered view.
Alternatively, use conditional runs in the column's Run Settings. Add an "Only run if" condition that targets specific criteria for the rows you want to process. [1] You can use the "Use AI" button to create conditions in plain language. [2]
Clay Support
APP
·
·
Is this helpful?
Rutger B.
·
·
bro that’s way too complex for what is problem on Clays side
Rutger B.
·
·
This table worked fine yesterday and many days before
Rutger B.
·
·
get me in touch with a human - thanks

28 comments