I started getting this error in Firebase Studio Prototyper. The interesting part is that gemini, which worked successfully last night, gave this warning in the first message I sent when I woke up in the morning. It would make sense if it gave this warning after sending a continuous request, but I thought it might be a systemic error because I saw this warning in my message after not using it for hours, although I never saw such an error until the last message I sent. I saw that a few people started to have the same problem in the last day. How is the situation with you?
1 Like
I think it’s because of my backlog of messages. Past chat messages seem to create a huge token load. I think this is causing the system to generate too many request errors. I’ve heard that this will be fixed in the future, but for now the workaround seems to be to reset the chat history with /clear call.
For those who are curious: After resetting with /clear it doesn’t forget the history completely. I don’t know what it forgets and how it works, it seems to remember everything. But it still works for now.
1 Like
if you want to fully clear or modify your chat history, you can look and follow this post’s steps.
1 Like
Too many requests seems like a message that comes from the Google Gemini model you’re using. Are you still connected to a “preview” model like “gemini-2.5-pro-preview-06-05”?
Built-in gemini model is selected. I just reached the context limit. Therefore it made the most sense to clear the history.