For general issues in Clay, try clearing your browser cache and refreshing the page. You can also perform a hard refresh: - Mac: Cmd + Shift + R (Chrome/Firefox) or Cmd + Option + R (Safari) - PC: Ctrl + F5 (Chrome/Firefox/Edge) If you're experiencing specific issues with stuck processes or queued cells, a hard refresh using Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) often resolves these problems. If you need further help, click "Talk to a person" for human assistance.
Iāve increased the column limit for you. Just keep in mind that adding too many columns can affect performance, so try to keep it manageable. For the cell size issue, since Clay has a character limit per cell, a good workaround is using a formula to extract or break down the data. You could, for example, extract the first 4,000 characters or another one is to filter for specific technologies before running enrichment
Let me know if you want help setting that up.
All setāI added a formula column called First 4000 Characters, and youāll see it in your table now. That should help with the cell size issue, though I didnāt spot any specific cells currently showing errors. Let me know if thereās another one I should look at.
hmm still running into issues, I outlined 3 here:
BuiltWith
time out issue
enrichment date best practice
loom is here - https://www.loom.com/share/4ecfbbe2b5d84907bc52af883b50933d?sid=27267f86-6441-4fac-ba6b-572fd45dd2d8
Hey!
For limiting the technologies pulled in your enrichment, the best option is to filter or pre-select only the technologies you care about, rather than pulling the full stack. You can also use a ālast updatedā filter to keep things less large (i.e a shorter timeframe)
For rerunning timeouts: you can click the column header > āRunā > āRun all rows that didn't run or have errorsā to retry only the ones that didnāt go through. Timeouts can happen due to API limits, model constraints, or volumeāso this will help target just the incomplete ones.
If youāre using an older template, itās possible somethingās outdated. We push updates regularly, so if youāre seeing strange behavior, try recreating the column or using a new table to test performance.
Lastly, for tracking enrichment dates, you can use a formula like this to log when a row was enriched: LBKS{{/AI Support Opportunities}} || 1 ? new Date().toISOString() : ""LBKSJust replace the column name with the right one from your table. This will store the current timestamp only when the enrichment result exists.
Let me know if you have more questions.
.png){kind=logo}
