Join the Community

Home
Directory
Events

00 Clay Announcements
01 Community General
01 Props and Wins
01 Watercooler
01 Welcome and Intros
02 Bugs
02 Starting with Clay
02 Support
03 Feedback & Requests
03 Tutorials & Inspiration
04 FT Job Opps

Community Guidelines

Powered by Tightknit

Troubleshooting Runtime Errors in Claygent Enrichment Process

·

Hi there, Im getting runtime errors when running a claygent enrichment. It happens with and without the clay provided api key. It seems to be on this table only https://app.clay.com/workspaces/206246/workbooks/wb_0swqcblrJrdJ2g8dscD/tables/t_0swrwtugbWw8CrHJi2Y/views/gv_0swrwtudYw6xDdQXm69

7 comments

Channeled
APP
·
·
There could be several reasons for runtime errors with a Claygent enrichment on a specific table: 1. API key issues - even if you've tried both with and without the Clay-provided key, ensure your API key is correctly copied from your account settings (Account → API key). 2. Table configuration problems - the error might be related to: • Writing to deleted columns • Referencing tables incorrectly • Misconfigured integration sequence 3. Input data formatting - ensure your data is properly formatted for the enrichment. Could you share the specific error message you're receiving? This would help me troubleshoot your issue more effectively.
Sources: Enrichments | Documentation | Clay University Write to Other Table | Documentation | Clay University Find your Clay API key | Documentation | Clay University
Michael W.
·
·
The error is "Runtime Error"
Michael W.
·
·
https://app.clay.com/workspaces/206246/workbooks/wb_0swqcblrJrdJ2g8dscD/tables/t_0swrwtugbWw8CrHJi2Y/views/gv_0swrwtudYw6xDdQXm69
Michael W.
·
·
Looks like its occuring on other tables too (Look at the negative news URL col in this table) https://app.clay.com/workspaces/206246/tables/t_0swqhdjj5s9xe3fHyFB/views/gv_0swklexHMTNnB4yHd7w
Bo (.
·
·
Hey, sorry about this — it looks like there’s a bug on our end. We’ve escalated it to the engineering team and will follow up as soon as we hear more. In the meantime, a workaround that’s been helping others is to recreate the same column in a new one. That should get things running again for now.
Bo (.
·
·
Good news! Happy to report that we heard back from the team and this issue should be fixed. Older AI columns should work again. 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.
1
Michael W.
·
·
Thanks Bo, much appreciated!