claybot- how long should it take for a simple work email enrichment on 1200 rows? the table has been updating for over an hour so far. https://app.clay.com/workspaces/507736/workbooks/wb_0szv2luxXUbsormVAYw/tables/t_0szv63gyxKs7G4Wa3aG/views/gv_0szv63v2XgRwcgqxvcB
Work email enrichments on 1200 rows taking over an hour suggests potential performance issues. This could be due to API tier limits - with lower tier APIs (like tier 1), you'll need to process data in smaller batches of around 50 rows at a time. Performance may also be affected when there are large tables and multiple actions running simultaneously, causing latency where cell data takes longer to load. To troubleshoot: ** Try clicking the column header and selecting "Force" to jump start the run ** Toggle auto-update off and on again, then accept the run prompt * Consider processing in smaller batches if using lower-tier API limits
Hi Adam, thanks for reaching out to support! Are you still having issues with your work email enrichment
The clay table stayed in "updating" mode over night. I had to force stop it. Last night, it ran for an hour. The I "forced run" the table for 3.5k credits and it kicked back in and almost completed the work email waterfall. Now it says for 7.5k credits i can rerun the table. Why do I need to spend 3.5k extra credits to make the table run? and still the table is not complete. here's the table. you will see it's still updating even after ticking the box to stop and accepting the terms of stoping it. https://app.clay.com/workspaces/507736/workbooks/wb_0szv2luxXUbsormVAYw/tables/t_0szv63gyxKs7G4Wa3aG/views/gv_0szv63v2XgRwcgqxvcB
Hey Luca P. i am working on 2 computers. the clay table looks right on the pc. my mac is not working so well with clay. not sure why the difference. i only have slack on the mac, so it's a hassle to send you a link from the other computer. I think i'm good to go right now (besides the part about my mac not working).
Hi there! I understand your frustration with the table getting stuck in "updating" mode and the credit consumption issues. Let me address your concerns: Regarding the Table Stuck in "Updating" Mode: This is a known issue that can occur with Clay tables, especially during longer runs or with larger datasets. Here are the key points: ** Force stopping sometimes doesn't immediately reflect: Even after clicking "stop" and accepting the terms, the table may still show as updating due to UI sync issues ** Browser differences: You're absolutely right about the Mac vs PC difference - this is actually a documented issue where Clay performs differently across browsers and operating systems ** Mac compatibility: Clay works best with Chrome-based browsers (Chrome, Edge, etc.). Safari and older browser versions can cause performance issues and display problems About the Credit Consumption: The way Clay's credit system works during interrupted runs: ** Partial completion: When a table stops mid-run (due to timeout, force stop, or technical issues), you're only charged for data that was successfully retrieved ** Rerun costs: The additional 3.5k credits for the rerun represents the remaining work that needs to be completed ** Waterfall pricing: Each enrichment step in your waterfall costs different amounts of credits based on the data provider and complexity Immediate Solutions: 1. For the Mac issue: Try using Chrome instead of Safari, or test on your PC where it's working properly 2. For stuck tables: Sometimes duplicating the problematic column and re-running can resolve stuck enrichments 3. Browser optimization: Disable browser extensions temporarily, clear cache, and ensure you're using an updated Chrome version Why the Credit Difference: The 7.5k total vs your original run reflects that some enrichments may have failed or timed out during the overnight run, requiring additional credits to complete the full waterfall for all rows.
Ok thx. Appreciate the insights. We can close this out. Cheers!
I'm glad everything worked out! I'll go ahead and close out this ticket now, but don't hesitate to reach out again if you need any help in the future.
.png){kind=logo}
