Munnawar H. Thanks for the update. Are you positive this is unrelated to the switch we made between our own API key back to credits? Perhaps our account got deprioritized on the Clay side when we made the switch to our own API key and when switched back to credits, we aren't getting pulled into the correct gemini Clay queue to run?
We are completely stuck which is odd especially as I have tried running just a single record at different times of day and it never processes.
Do you have an ETA on these improvements?
Switching models isn't a great solution as different models provide different hit rates and varying degrees of accuracy. We have spent a considerable amount of time testing and refining the Gemini model. Plus we built 2026 budgets & forecasting has been done using the expected results of Gemini. This is the top of our sales funnel and switching models will have a significant impact to our business plan and operations.
We have already experienced a hiccup when the cost estimates to AI provider provided by Clay was inaccurate and our actuals of running our Gemini API was 8x the estimated cost provided by Clay. This is what prompted the switch back to using Clay credits. Now we are completely stuck until improvements are made by the Clay team with Google as we cannot run this enrichment even with credits. Or we are forced to pay 8x the estimated cost to use our own API.
