My Gemini enrichment was originally set-up to utilize our personal API key which worked fine. I have since changed it to use the Clay Managed - 1 Credit version. When I run the enrichment (also tried to force run), it appears to run the enrichment then times out or I get an error message. I have been trying for the past 3 days to get this enrichment to run. How can I resolve this issue? Table
The error you're seeing is related to Google Gemini's rate limiting. Even with Clay-managed accounts, Google Gemini AI Studio runs on shared capacity and can hit constraints during heavy usage periods.
Try these steps to resolve it:
Force run the column: Click the column header, hover over "Run column field" and select "Force" to jump start the enrichment.
Toggle auto-update: Turn off auto-update for the column, then turn it back on and accept the run prompt to refresh all rows.
Wait and retry: Since this is a capacity issue on Google's end, try running the enrichment during off-peak hours when there's less demand on their shared infrastructure.
Before we escalate this further, I'd recommend trying our built-in AI tool Sculptor (top-right corner of your screen) to help troubleshoot and potentially rebuild this enrichment with optimized settings. Let me know if Sculptor helps or if you're still having issues after trying these steps.
Is that what you were looking for?
If you still need help resolving the Gemini enrichment issue, I’m here to assist you further. Would you like to provide more details about what you’ve tried or any other challenges you’re facing?
What are considered non-peak hours?
Also, the error message received is not related to timing out. This appears to be an issue within Clay. Will you please review?
You're right - this specific error "function call turn comes immediately after a user turn or after a function response turn" is a Google Gemini API formatting issue, not a rate limit problem.
This error typically happens when there's a conversation flow issue in how Clay is structuring the API calls to Gemini. Try these steps:
Force run the column: Click the column header, hover over "Run column field" and select "Force" to restart the enrichment.
Toggle auto-update: Turn off auto-update for the column, then turn it back on and accept the run prompt to refresh all rows.
Clear and reconfigure: Delete the current Gemini enrichment column and recreate it with the same settings - this often resolves API formatting issues.
Before we go further, try using Sculptor (top-right corner) to help rebuild this enrichment with optimized settings. Let me know if Sculptor helps or if you're still seeing this specific error after trying these steps.
Did that answer your question?
I have tried those recommendations and it doesn't work.
Since the standard troubleshooting steps haven't resolved this specific Gemini API error, this looks like it needs deeper investigation into your table configuration.
Before we connect you with a human agent, try using Sculptor (top-right corner of your screen) to help diagnose and potentially rebuild this enrichment with optimized settings. Sculptor can often identify configuration issues that cause these API formatting errors.
Let me know if Sculptor helps resolve the issue or if you'd still like to speak with a human agent after trying it.
Was this helpful?
I already tried your recommendations. Please connect me with a human agent. Thanks!
Got it — I’m connecting you to a human teammate now.
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!

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!
