-
Notifications
You must be signed in to change notification settings - Fork 161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gemini API returns 503 error with MissingFieldException #220
Comments
I think adding the missing field will give some inshights to the error that's happening in Google's side. It's a weekend so I doubt that that the team will be able to take a look at it today or tomorrow. This is the error I'm also getting
|
Hi @surajsahani, Were you getting the errors earlier also?? I mean whether it was working earlier and suddenly you started seeing these errors or from very beginning you were getting these errors? |
This issue started suddenly from last 4-5 days @gmKeshari |
+1 This has been happening from last week, when new gemini model drop for Iphone |
Hey @surajsahani, Due to overload this issue was reported by many users last week. Our team is working to fix this. You can consider this as a temporary issue. Temporarily switch to another model (e.g. from Gemini 1.5 Pro to Gemini 1.5 Flash) and see if it works. Or wait a bit and retry your request. |
Description of the bug:
When interacting with the Gemini API, the following error message is received in the log:
This indicates that the API is overloaded, but it also throws a MissingFieldException related to the 'details' field when parsing the response.
Actual vs expected behavior:
Actual: The response includes a 503 error code with the message "The model is overloaded." Additionally, a MissingFieldException is thrown due to the missing 'details' field.
Expected: The API should either provide a valid response with the necessary 'details' field or handle missing fields gracefully without throwing an exception.
Any other information you'd like to share?
This error occurs during normal API interaction when the model is under heavy load. It would be helpful to have the API gracefully handle missing fields in error responses to prevent application crashes.
The text was updated successfully, but these errors were encountered: