Troubleshooting Runtime Errors in Claygents: Seeking Help

Rubina C. · 2025-10-22 08:20:21.486128+00

Is anyone having issues with Claygents? I'm keep getting Runtime Errors. 🤔

Troubleshooting Runtime Errors in Claygents: Seeking Help | Clay

10 comments

· Sorted by Oldest

Clay Support
APP
·
·
Runtime errors with Claygent are often related to API tier requirements or rate limits. First, clear your browser cache and refresh the view to resolve error messages.
For Claygent to work properly, you need an OpenAI API key with Tier 2 or higher (≥450,000 TPM). Check your API usage tier at https://platform.openai.com/settings/organization/limits to ensure it meets requirements.
Recent updates to Claude Sonnet 3.7 integration have doubled estimated token usage per Claygent run, which can cause more rate limit issues. We're deploying features like retries and smarter pacing to better handle rate limits.
To troubleshoot further:
Ensure your search queries are specific and well-defined
Break large data requests into smaller batches
Monitor your API quotas and usage limits
If your API key is correct but you're seeing warnings, consider upgrading to a higher tier for better performance.
Clay Support
APP
·
·
Did that answer your question?
Rubina C.
·
·
No, because I'm using Clay > Argon, not OpenAI.
Clay Support
APP
·
·
I understand the frustration with the issue you're facing. I'll connect you to a human agent who can assist you further.
Intercom
APP
·
·
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!
Loading attachments
Soumaya R.
·
·
Hello, I'm experimenting the same issue !
Rubina C.
·
·
Good to know I'm not alone. 🙂
Munnawar H.
·
·
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.
Rubina C.
·
·
Amazing, thanks so much Munnawar H. for the update.
Clay Support
APP
·
·
We haven't heard back from you here, so we're going to go ahead and close this thread out.
Still need help here? Reply back and someone will jump back in.
Have a question thats not related to this thread? We recommend kicking off a new ticket in the support channel!

Clay Support
APP
·
·
Runtime errors with Claygent are often related to API tier requirements or rate limits. First, clear your browser cache and refresh the view to resolve error messages.
For Claygent to work properly, you need an OpenAI API key with Tier 2 or higher (≥450,000 TPM). Check your API usage tier at https://platform.openai.com/settings/organization/limits to ensure it meets requirements.
Recent updates to Claude Sonnet 3.7 integration have doubled estimated token usage per Claygent run, which can cause more rate limit issues. We're deploying features like retries and smarter pacing to better handle rate limits.
To troubleshoot further:
Ensure your search queries are specific and well-defined
Break large data requests into smaller batches
Monitor your API quotas and usage limits
If your API key is correct but you're seeing warnings, consider upgrading to a higher tier for better performance.
Clay Support
APP
·
·
Did that answer your question?
Rubina C.
·
·
No, because I'm using Clay > Argon, not OpenAI.
Clay Support
APP
·
·
I understand the frustration with the issue you're facing. I'll connect you to a human agent who can assist you further.
Intercom
APP
·
·
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!
Loading attachments
Soumaya R.
·
·
Hello, I'm experimenting the same issue !
Rubina C.
·
·
Good to know I'm not alone. 🙂
Munnawar H.
·
·
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.
Rubina C.
·
·
Amazing, thanks so much Munnawar H. for the update.
Clay Support
APP
·
·
We haven't heard back from you here, so we're going to go ahead and close this thread out.
Still need help here? Reply back and someone will jump back in.
Have a question thats not related to this thread? We recommend kicking off a new ticket in the support channel!