.png){kind=logo}
Enrichment Columns Displaying Runs: New Update Overview
enrichment columns are now showing runs? like this? https://app.clay.com/workspaces/16336/workbooks/wb_WRCkhpkAZwsc/tables/t_wdZvuz3yxnTo/views/gv_HeTREBXejp2d
If enrichment columns are showing as "queued" or not running properly, this could be happening for a couple of reasons: 1. The enrichment might have run before all necessary data was updated. To fix this: • Re-update your data first • Add conditional run settings to only run when all required variables are present 2. If cells are stuck in a queued status, try performing a hard refresh: • Windows: Press Ctrl + Shift + R • Mac: Press Cmd + Shift + R Also, check if there are any dependencies between columns. If so, make sure to remove run conditions from dependent columns and set them to only run when the required data is present.
Did that answer your question?
Looks like you're still looking for help. We're currently outside of our standard office hours (9 AM to 9 PM EST, Monday through Friday), so it may take a little longer for us to respond. 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!
It's still happenning to a lot of other tables. where i have to wait for 1 min before it shows enrichment
Bo (.··Hi Harvey, Great to hear it's working now! Let me know if you need anything else.
this Bo (. - my lead magic is working with other column but verifying prospeo, it's showing this. https://app.clay.com/workspaces/16336/workbooks/wb_M6QCrsaUriQb/tables/t_z66Qm49Efiyb/views/gv_DBF6PhqbicV5
- Bo (.··
Hi Harvey! Let's update your API key to fix the Lead Magic error.
(1247 kB)
For the lag - could you share which specific actions are running slow? That'll help me pinpoint this
Let me know
lag - inputing text into a new column. running normalize company name, http ai calls
everything pretty much
Also this column is not running
- Bo (.··
Hi Harvey!
I've flagged this to our engineers to investigate. For the awaiting callback status, this is normal behavior while waiting for provider responses. They should come through soon. Let me know if you see any other issues or need help with anything else!
- Bo (.··
Hi Quick follow up on the sluggish performance - this will help us better understand your situation as well: Does this happen with a specific table or across all tables? Also, is this a new issue or has it been happening for a while? And lastly, do you notice it getting worse in certain situations (like after having Clay open for a long time)? Let me know and I'll help get this sorted out.
many different table. Happens with enrichment rows just yesterday. worse if you have multi table or complex conditional runs
Mark L.··Harvey, thanks for those details! When you say "just yesterday", do you mean it was only bad yesterday (and is now improved), or it just started yesterday (and is still ongoing). And would you be able to share some specific tables where this seems to be worse? I spot-checked on a dozen or so to compare, but I'm not getting the same symptoms you have. So I'd appreciate a pointer on an especially troublesome example or two. I'm also curious for high-level detail on your computer setup – make/model/CPU/RAM, browser version, etc.? That may help assess as well.
Hey Mark - it's gotten better. My specs. browser - chrome.
could be my internet as well, but calls and everything else have no issues
- Mark L.··
Hey, that's great! Glad there's been some improvement! Please keep me posted if you're working in any specific tables, and you see sluggishness like you did before. I'd be very interested to take a peek and share with the team.
curious tho - our enrows enrichment have been sitting awaiting on call back
- Mark L.··
Mind linking to the specific table you're concerned with? I didn't spot that in the two mentioned earlier in the thread.
(52 kB)
- Mark L.··
Thanks, Harvey. I re-ran a couple dozen rows, and it looks like they are resolving. It's not expected that they would stay in the "Awaiting callback..." state. My understanding is that the provider sometimes takes a very long time to reply, though, so Clay is not able to resolve. I've shared this with the engineering team, so that they can work with the provider to help iron this out. In the meantime, you can re-try the rest of the rows, if you're ready to run it.
got it
thanks Mark
- Mark L.··
You're welcome!