Is clay down right now? we've been getting a lot of "unable to retrieve data" and some of the cells are even running for more than half an hour now
This looks like stuck enrichments rather than Clay being down. Try these quick fixes:
For stuck cells: Click the column header → hover over "Run column" → select "Force" to restart the column
For queued cells: Click the column header and select "Force Rerun Column" to reset it
Performance issues: Try a hard refresh (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac) as this can resolve loading delays with larger tables
If cells show "waiting for inputs," click "re-run this cell" or toggle auto-update off and on
No additional charges apply when re-running stuck rows
Did that answer your question?
If you still need help resolving the stuck cells or data retrieval issues, I’m here to assist. Would you like to provide more details about what you’re trying to achieve so I can support you further?
nope it did not fix our issue
Sorry to hear that the issue persists. I’m routing you to our human team now for further assistance.
I need a live support
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!

this issue is present in both of these workspaces
Hey John! Thanks for reaching out. This as of late has been typical behavior for larger datasets and I see you're working between 20-30k+ rows so it is expected to take longer to process.
How long ago did you run it?
It ran for more than half an hour then reached ‘time-out’
Hmm. Could you attempt a hard refresh and run those again? Preferably in smaller batches before as a large group.
Mac:
Chrome and/or Firefox = Press Cmd + Shift + R
Safari = Press Cmd + Option + R
PC:
Chrome, Firefox, Microsoft Edge = Press Ctrl + F5
already did but still has the same issue
Hi John,
Thank you for reaching out to the support team, I can't seem to find any timeout errors in the table you've linked, are you still experiencing timeouts here? If so, had you experienced this before, or is this behaviour new for this table? Any further context you provide will help us troubleshoot here.
