Groq
meta-llama/llama-4-scout-17b-16e-instruct model retirement
Stopped workingSubscribe to GroqShare
On July 17, 2026, the model meta-llama/llama-4-scout-17b-16e-instruct was retired for users on free and developer tiers. Requests specifying this model fail since that date. The change affects calls targeting model meta-llama/llama-4-scout-17b-16e-instruct on these tiers.
The error you get
What Groq answers a call to meta-llama/llama-4-scout-17b-16e-instruct once the model is gone, as recorded from real responses:
{"error":{"message":"The model `meta-llama/llama-4-scout-17b-16e-instruct` does not exist or you do not have access to it.","type":"invalid_request_error","code":"model_not_found"}}What to use instead of meta-llama/llama-4-scout-17b-16e-instruct
Move to openai/gpt-oss-120b. The alternative replacement qwen/qwen3.6-27b also stopped working on September 14, 2026.
In Groq's words
Deprecated Model: meta-llama/llama-4-scout-17b-16e-instruct; Shutdown Date: 07/17/26; Recommended Replacement Model ID: openai/gpt-oss-120b or qwen/qwen3.6-27b
Facts
- API
- Groq
api.groq.com - Model
meta-llama/llama-4-scout-17b-16e-instruct- Released
- April 5, 2025 (models.dev)
- Kind
- Model retirement
- Takes effect
- July 17, 2026
- Calls after that day
- Fail
- Who it affects
- free and developer tiers
- Source
- Deprecations page
- Last updated
- Verified
- , against Groq's own pages
Questions
When does meta-llama/llama-4-scout-17b-16e-instruct shut down?
Calls to the model meta-llama/llama-4-scout-17b-16e-instruct on Groq stopped working on July 17, 2026.
What happens to calls after July 17, 2026?
They have failed since July 17, 2026.
What error does meta-llama/llama-4-scout-17b-16e-instruct return once it is shut down?
Groq answers HTTP 404: "The model `meta-llama/llama-4-scout-17b-16e-instruct` does not exist or you do not have access to it.". Send another model to fix it.
When was meta-llama/llama-4-scout-17b-16e-instruct released?
meta-llama/llama-4-scout-17b-16e-instruct was released on April 5, 2025, 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.
meta-llama/llama-4-scout-17b-16e-instruct on other APIs 3
-
SambaNova Cloud
llama-4-scout-17b-16e-instructModel retirement Stopped working -
Together AI
meta-llama/llama-4-scout-17b-16e-instructModel retirement Stopped working -
Azure AI Foundry
llama-4-scout-17b-16e-instructModel retirement Stops workingin 86 days
More from Groq 10
-
playai-ttsModel retirement Stopped working -
meta-llama/llama-guard-4-12bModel retirement Stopped working -
meta-llama/llama-4-maverick-17b-128e-instructModel retirement Stopped working -
moonshotai/kimi-k2-instruct-0905Model retirement Stopped working -
qwen/qwen3-32bModel retirement Stopped working -
llama-3.1-8b-instantModel retirement Stopped working -
llama-3.3-70b-versatileModel retirement Stopped working -
qwen/qwen3.6-27bModel retirement Stopped working -
groq/compoundModel retirement Stopped working -
groq/compound-miniModel retirement Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.