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.
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.
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!
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.