Still experiencing Runtime error in my table: seems like only claygents are affected
For runtime errors affecting Claygents, try these solutions:
Quick fixes:
Clear your browser cache and refresh the view
Click the column header → hover over "Run column" → select "Force" to jump start the run
Alternative run options:
Right-click the column → "Run All Rows that haven't run or have errors" [1]
Use "Force Run All Rows" if needed
AI troubleshooting:
Click any error cell and select "Troubleshoot with AI" for tailored debugging instructions [2]
If you need further help, request human assistance by clicking on "Talk to a person."
Did that answer your question?
If you still need help resolving the runtime error with your Claygents, I’m here to assist. Would you like to provide more details about the issue you’re encountering so we can continue troubleshooting?
connect to an agent
I’m routing you to our human team now. They’ll be able to assist you further.
Clay Support is sharing a file with you.
Our support team has got your message and we'll get back to you soon! 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!
Hi there,
Thank you for reaching out to the support team. We are currently experiencing an issue with Claygent columns in some customer workspaces.
Our engineering team is actively working on a fix, and we will update you as soon as it has been resolved.In the meantime, a temporary workaround is to recreate the affected columns and rerun them.
We apologise for the inconvenience and appreciate your patience while we work on a solution.
Hi there, Good news,
The issue affecting Claygent columns has now been fully resolved. Everything should be running normally again, and you shouldn’t see any more runtime errors. Feel free to rerun any columns that experienced the issue. Thanks so much for your patience and understanding while we worked on getting this fixed.
If you are still experiencing issues here, please let us know.
