Home

Clay Announcements
Clay Support
Discuss Anything
Feedback & Requests
GTM Career Advice
Introduce Yourself
Member Spotlight
Share Content and Events
Share Full-time Jobs
Share Part Time Jobs
Share Tables, Tools, and Workflows

Community Guidelines

Explore Events
Learn Clay here
Clay Cup

Powered by Tightknit

Concern About Speed Issues with Claygent on Usage Tier 5 | Clay

Concern About Speed Issues with Claygent on Usage Tier 5

·Aug 06, 2025 06:50 PM·

I’m on usage tier 5 with open ai but claygent has been running really slow for days. What’s going on

4 comments

· Sorted by Oldest

Clay
APP
·
·
Even with OpenAI usage tier 5, Claygent slowness can occur due to several factors. First, check if you're seeing yellow warnings in Clay - this indicates low limits on your account may cause slow performance. To address processing delays: - Ensure your search queries are specific and well-defined - Break large data requests into smaller batches - Monitor your usage limits, tiers and API quotas - Check your network connection stability For reliable Claygent performance, you need 450,000 TPM (tokens per minute). Even at tier 5, if your current TPM allocation is being heavily used or you're hitting rate limits, this could cause slowdowns. You can verify your current usage and limits at OpenAI's platform to see if you're approaching your tier's boundaries.
Luca P.
·
·
Kevin - Sorry for this, it looks like we've got a bug on our hands. I've escalated this to our engineering team to help look into it. We'll follow up here as soon as we know more!
Clay
APP
·
·
Hi there - thank you for your patience while our Engineers identified and fixed this issue. We're sending out a confirmation to all customers that reported an issue that everything should be resolved. Please let us know if anything is still not functioning as expected in your account. And thank you again for reporting the issue!
Luca P.
·
·
Good news! Happy to report that we heard back from the team and this issue should be fixed. 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.