Table Crash Issue: Need Assistance with Troubleshooting

Aditya K. · 2025-07-29 11:59:38.888488+00

Hey Team, my table has just stopped working and it seems to have crashed. I tried waiting for the last 2 hours, but it is still the same. Attaching the image in the thread below

Table Crash Issue: Need Assistance with Troubleshooting | Clay

12 comments

· Sorted by Oldest

Aditya K.
·
·
Loading attachments
Clay
APP
·
·
Try a hard refresh first: ** Windows: Ctrl + Shift + R ** Mac: Cmd + Shift + R If columns are stuck in "queued" status, click the column header and select Force Rerun Column to jumpstart the run. For persistent errors, clear your browser cache and refresh. Performance issues often occur with larger tables or complex workflows running simultaneously.
Clay
APP
·
·
Since you've already tried a hard refresh and the table is still stuck, try clicking the column header of any stuck columns and select Force Rerun Column to jumpstart the run. If columns show "queued" status, this often happens when columns were changed multiple times or runs were stopped midway.Clear your browser cache completely and refresh again. Performance issues commonly occur with larger tables or complex workflows running simultaneously.
Aditya K.
·
·
https://app.clay.com/workspaces/526456/workbooks/wb_0sz14egrQ3M9CCW4G5R/tables/t_0sz14gohAZmtgW2KyvT
Aditya K.
·
·
guys need help here!?
Luca P.
·
·
Hi Aditya, thanks for reaching out to support! The earlier latency issues affecting some Clay tables have now been resolved. Everything should be loading as expected again. Thanks so much for your patience while we worked through it! If you're still experiencing any issues, please let us know.
Aditya K.
·
·
Hey Luca, thanks for reaching out. The table is still not working.
Loading attachments
Luca P.
·
·
Hi Aditya, thanks for reaching out to support!
Let me take a quick look at your table here to see what is going on
Luca P.
·
·
Hey there, thank you for reaching out about this issue and for trying the troubleshooting steps. We’re aware that some users have been reporting slowness and our engineering team is looking into it! And our status page will automatically update if a global issue is identified across many accounts. In the meantime, we are still working to narrow down the exact behaviors to replicate the slowness and identify specific actions in the product that are causing this issue. Please let us know if there's anything else we can do to help in the meantime! :)
Aditya K.
·
·
Hey Luca, just to let you know, the table is still not working and is crashed. The status page shows all systems are good, but clearly there is a problem. It would be really great if this can be solved and the table can be restored as the workflow was quite important and has to be provided to a client soon.
Luca P.
·
·
Aditya - Sorry for this, it looks like we've got a bug on our hands. I've escalated this to our engineering team to help look into it. We'll follow up here as soon as we know more!
LuisArturo
·
·
Good news! Happy to report that we heard back from the team and this issue should be fixed. Try a quick refresh (Cmd/Ctrl + Shift + R) and let us know if the problem has been resolved on your end, or if you still have trouble. Thank you for your patience as we worked on it.

Aditya K.
·
·
Loading attachments
Clay
APP
·
·
Try a hard refresh first: ** Windows: Ctrl + Shift + R ** Mac: Cmd + Shift + R If columns are stuck in "queued" status, click the column header and select Force Rerun Column to jumpstart the run. For persistent errors, clear your browser cache and refresh. Performance issues often occur with larger tables or complex workflows running simultaneously.
Clay
APP
·
·
Since you've already tried a hard refresh and the table is still stuck, try clicking the column header of any stuck columns and select Force Rerun Column to jumpstart the run. If columns show "queued" status, this often happens when columns were changed multiple times or runs were stopped midway.Clear your browser cache completely and refresh again. Performance issues commonly occur with larger tables or complex workflows running simultaneously.
Aditya K.
·
·
https://app.clay.com/workspaces/526456/workbooks/wb_0sz14egrQ3M9CCW4G5R/tables/t_0sz14gohAZmtgW2KyvT
Aditya K.
·
·
guys need help here!?
Luca P.
·
·
Hi Aditya, thanks for reaching out to support! The earlier latency issues affecting some Clay tables have now been resolved. Everything should be loading as expected again. Thanks so much for your patience while we worked through it! If you're still experiencing any issues, please let us know.
Aditya K.
·
·
Hey Luca, thanks for reaching out. The table is still not working.
Loading attachments
Luca P.
·
·
Hi Aditya, thanks for reaching out to support!
Let me take a quick look at your table here to see what is going on
Luca P.
·
·
Hey there, thank you for reaching out about this issue and for trying the troubleshooting steps. We’re aware that some users have been reporting slowness and our engineering team is looking into it! And our status page will automatically update if a global issue is identified across many accounts. In the meantime, we are still working to narrow down the exact behaviors to replicate the slowness and identify specific actions in the product that are causing this issue. Please let us know if there's anything else we can do to help in the meantime! :)
Aditya K.
·
·
Hey Luca, just to let you know, the table is still not working and is crashed. The status page shows all systems are good, but clearly there is a problem. It would be really great if this can be solved and the table can be restored as the workflow was quite important and has to be provided to a client soon.
Luca P.
·
·
Aditya - Sorry for this, it looks like we've got a bug on our hands. I've escalated this to our engineering team to help look into it. We'll follow up here as soon as we know more!
LuisArturo
·
·
Good news! Happy to report that we heard back from the team and this issue should be fixed. Try a quick refresh (Cmd/Ctrl + Shift + R) and let us know if the problem has been resolved on your end, or if you still have trouble. Thank you for your patience as we worked on it.