I keep getting runtime error on a table that I use constantly and never has problems. The required fields are all there and it doesn't enrich any of the leads.
Other tables work
My API account is funded
I tried to log into a incognito browser and run it
I duplicated the table and tried to run it
I clicked force run and run all columns that have errors
Since you've already tried force run and the required fields are populated, try these steps to resolve the runtime errors in your "Business Description" column:
Delete the affected column
Create a fresh column with the same configuration
Re-map your data to ensure everything is properly connected
If the issue persists after recreating the column, try a hard refresh of your browser:
Windows: Ctrl + Shift + R
Mac: Cmd + Shift + R
Also verify that your input fields (like company domain or website URLs) are complete and valid in the rows showing errors.
If these steps don't resolve the runtime errors, click on Talk to a person for further assistance.
Is that what you were looking for?
If you still need help resolving the runtime error with your table, I’m here to assist. Would you like to provide more details about what you’re trying to achieve or any other issues you’re encountering?
It's still not working
I'm sorry to hear that the issue is still unresolved. I'll connect you to a human agent who can 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!
Same issue
Yes Most probably
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.
