Any update on when the Gemini rate limiting will be addressed?

Gemini rate limits are managed by Google, not Clay. To increase your limits, you'll need to upgrade your API tier directly with Google. [1]

We've implemented retries and smarter pacing to better handle rate limits and reduce errors. For immediate relief, try processing smaller batches of data to stay within your current limits.

Is that what you were looking for?

If you need any more help with the Gemini rate limiting or anything else, please let me know. Would you like to provide more details about what you're trying to resolve or understand?

This did not

I'm sorry to hear that. I'll connect you to a human agent who can assist you further.

Our support team has got your message and we'll get back to you soon!

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!

Hi Milo - thanks for reaching out!

Are you facing issues with Gemini currently? I believe we tried to deploy a few fixes. Let me know if those work - thanks!

I am still getting high error rates for the clay account one, better than than last week but still not ideal

Yea - I believe this might be due to the rate limits of Gemini, which stems from Google-sides. Unfortunately, theres no quick fix as of currently; I recommend trying other models or implement slower- steadier pacing requests!

There is no way to optimize or batch that has been found?

Unfortunately, no current way to optimize it except in small manual batches. However, this is something that we are currently working/focusing on improving!

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!