Bug: v13 gives "quota exceeded" on Gemini API while reverting back to v12.0 let the API work correctly. #694
Closed
justynabardzinska
started this conversation in
General
Replies: 1 comment
-
Dyad doesn't do any kind of rate limiting when you use your own API key. I'm guessing when you switched to v0.12, you waited long enough to go under the Gemini rate limit, but you'll hit the same rate limit any of the Dyad versions. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
While using the v13, the Gemini API quota is always exceeded, even on a fresh new account. Reverting back to v12 let the same API work correctly on the environment. I suppose there is an application bug or hidden constraint that's blocking the Gemini API requests or overloading them with the informational "exceeded quota" always appearing and no job completed as result
Beta Was this translation helpful? Give feedback.
All reactions