Vertex AI
gemini-3.6-flash model retirement
Stops workingSubscribe to Vertex AIShare
On November 19, 2026, the model gemini-3.6-flash reaches retirement. Any calls sent to model gemini-3.6-flash after this date will fail. This retirement affects all requests targeting this specific model ID directly on the platform.
The error you get from November 19, 2026
What Vertex AI answers a call to gemini-3.6-flash once the model is gone, as recorded from real responses:
{"error":{"code":404,"message":"Publisher model `projects/{project}/locations/{region}/publishers/google/models/gemini-3.6-flash` was not found or your project does not have access to it. Ensure you are using a valid model name and that the model is available in the specified region.","status":"NOT_FOUND"}}
What to use instead of gemini-3.6-flash
Move to the recommended replacement model ID gemini-3.8-flash.
In Vertex AI's words
Model ID: gemini-3.6-flash; Release date: July 21, 2026; Retirement date: November 19, 2026; Replacement model ID: gemini-3.8-flash
Facts
- API
- Vertex AI
aiplatform.googleapis.com - Model
gemini-3.6-flash- Released
- July 21, 2026 (models.dev)
- Kind
- Model retirement
- Takes effect
- November 19, 2026
- Calls after that day
- Fail
- Source
- Deprecations page
- Last updated
- Verified
- , against Vertex AI's own pages
Questions
When does gemini-3.6-flash shut down?
Calls to the model gemini-3.6-flash on Vertex AI stop working on November 19, 2026.
What happens to calls after November 19, 2026?
They fail from that day.
What error does gemini-3.6-flash return once it is shut down?
Vertex AI answers HTTP 404: "Publisher model `projects/{project}/locations/{region}/publishers/google/models/gemini-3.6-flash` was not found or your project does not have access to it. Ensure you are using a valid model name and that the model is available in the specified region.". Send another model to fix it.
When was gemini-3.6-flash released?
gemini-3.6-flash was released on July 21, 2026, according to models.dev.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
gemini-3.6-flash on other APIs 1
-
Lovable AI Gateway
google/gemini-3.6-flashModel retirement Redirectsin 13 days
More from Vertex AI 10
-
deepseek-ocr-maasModel retirement Stopped working -
deepseek-r1-0528-maasModel retirement Stopped working -
deepseek-v3.1-maasModel retirement Stopped working -
deepseek-v3.2-maasModel retirement Stopped working -
glm-4.7-maasModel retirement Stopped working -
glm-5-maasModel retirement Stopped working -
/v1beta1/projects/{id}/locations/{id}/extensions*Endpoint removal Stops workingin 20 days -
claude-sonnet-4-5Model retirement Stops workingin 24 days -
models claude-sonnet-4-5@*Model retirement Stops workingin 24 days -
gemini-live-2.5-flash-native-audioModel retirement Stops workingin 37 days
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix before November 19, 2026.