Why is claygent so slow since yesterday? Taking hours to run rows
Claygent slowdowns are typically caused by API rate limits or processing delays. Recent updates to Claude Sonnet 3.7 doubled token usage per run, making rate limits more noticeable on lower API tiers.
Quick fixes:
Process smaller batches (around 50 rows at a time) if you're on a lower Anthropic API tier
Monitor your API quotas and usage limits
Try a hard refresh: Mac (⌘ + Shift + R), Windows (Ctrl + F5)
Break large requests into smaller batches and ensure your prompts are specific and well-defined.
Was that helpful?
Its still taking so much time even though I ran on 20 rows. Been 30mins still run now complete
This suggests your API tier is too low for the current workload. With lower Anthropic API tiers (like tier 1), you need to process smaller batches - around 50 rows maximum.
Check your Anthropic API tier at console.anthropic.com/settings/limits and verify your rate limits. For reliable Claygent performance, you need 450,000 TPM (tokens per minute).
Try a hard refresh: Mac (⌘ + Shift + R), Windows (Ctrl + Shift + R). If issues persist, consider upgrading your API tier for better performance.
Did that answer your question?
I understand the delay is frustrating, and I’m here if you need more help resolving the slow processing issue. Would you like to provide more details about your current setup or any other challenges you’re facing?
Connect me to a human
I’m routing you to our human team now. They’ll be able to assist you further.
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!

Claygent isn’t running it’s stuck on a loop. Force stopped, tried again, still not working
Hey Amna! Sorry for the trouble- Claygent has been running slow since yesterday and we're currently working to mitigate the problem. Do you mind showing me the table so I can check it out?
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!
