Jamba 1.5 Large — Retired

Quick fix — copy & paste

Choose your language. The "before" block matches the deprecated call; the "after" block is the drop-in replacement.

# Vertex AI: Jamba 1.5 Large (retired)
model = "Jamba 1.5 Large"

# No direct replacement — see Vertex AI docs.
# Pick a current model from the provider's available list.

// Vertex AI: Jamba 1.5 Large (retired)
const model = "Jamba 1.5 Large";

// No direct replacement — see Vertex AI docs.
const model = "<choose a current model>";

"model": "Jamba 1.5 Large"

"model": "<choose a current model>"

This migration was generated automatically from the model rename. If your code does more than swap a model id, double-check request/response shapes against the official Vertex AI migration guide.

Error messages

Seeing one of these? You're in the right place.

• model_not_found: Jamba 1.5 Large
• The model `Jamba 1.5 Large` has been deprecated
• The model `Jamba 1.5 Large` does not exist or you do not have access to it

Other Vertex AI deprecations

• Claude 3.7 Sonnet 2026-05-11 · 3d
• Claude 3.5 Haiku 2026-07-05 · 58d
• Claude 3 Opus 2026-08-01 · 85d
• Anthropic's Claude 3 Haiku 2026-08-23 · 107d

What this means for your code

Jamba 1.5 Large is a general-purpose chat model used through the standard messages or chat completions endpoint. Most production traffic on chat models comes from streaming responses, function calling, and tool use. After the shutdown date, every API call returns an error and your app breaks for end users until the model id is updated.

Jamba 1.5 Large was retired by Vertex AI on 2026-02-27. API calls now return an error and the model is no longer accessible. New code should use the recommended replacement; legacy code that still references this model id needs to be updated immediately.

Find every call in your codebase

Before you change anything, locate every place the deprecated model id is referenced. Search source files, environment files, feature flags, and config repos. Use these commands from your project root:

grep -rn '"Jamba 1.5 Large"' --include="*.py" .

grep -rn '"Jamba 1.5 Large"' --include="*.{js,ts,tsx,jsx}" .

grep -rn "Jamba 1.5 Large" .

Migration checklist

Steps in order. Skip any that don't apply, but read the whole list — for chat models, the non-obvious steps are usually the ones that break in production.

1. 1. Search for the deprecated model id in your application code, environment variables, and feature flags
2. 2. Update the model id in your API client configuration
3. 3. Re-run integration tests that exercise streaming, function calling, and structured outputs
4. 4. If you use prompt caching, verify the new model supports the same cache scopes
5. 5. Compare token costs on a representative sample of prompts before deploying