> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gloo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Fallback Chains

> Create and order fallback chains: the ordered model lists an agent dispatches from, with per-model weight and disabled-model warnings.

**Fallback Chains** (`/platform/fallback-chains`) holds named, ordered model lists. An agent assigned an active chain dispatches from the chain, not from its default model, even when the default model is healthy: Forge tries the chain's models in priority order and moves to the next one on a temporary provider failure (a rate limit, timeout, conflict, server error or failed connection) or a credential refusal (401 or 403). Other errors, such as a rejected request, fail the call. Forge uses the agent's default model only when the chain is missing, inactive or has no usable model, or when a call names a model explicitly. It is the **Fallback Chains** tab of the **Models** sidebar entry, after **Catalog** and **Providers**. Open it to add a backup model, reorder a chain, or find out why a chain has a disabled model in it.

![Fallback chains (light)](https://mintcdn.com/gloo-b243725a/xyq5perq6SLByPBn/forge/images/console/platform/fallback-chains-light.png?fit=max\&auto=format\&n=xyq5perq6SLByPBn\&q=85\&s=322318f5422b3cfe7bbb81ab832d7ca2)

Fallback chains — Forge Console at `/platform/fallback-chains`

## What you can do

* **New Fallback Chain** opens a drawer with **Name**, **Description**, and an ordered model list. Pick a model and click **Add**; set a **weight** per model; use the up and down arrows to reorder; remove a model with its remove control. The first entry is the highest priority. Save with **Create chain** or **Save changes**.
* Toggle a chain card's switch to activate or deactivate the chain.
* **Edit** reopens the drawer for that chain.
* **Delete** removes the chain after a browser confirmation ("This cannot be undone.").

A chain must have a name and at least one model; the drawer shows "Name is required" or "Add at least one model" otherwise.

## Chain cards

Each card lists the chain's models in priority order as `#<priority>`, the model's display name, and its `provider:modelId`. The stat cards count **Total Chains**, **Active** chains, and chains **With Disabled Model**.

| Model badge | Meaning | What to do |
| - | - | - |
| **not in catalog** | The chain names a model the catalog does not have | Replace it, or sync the provider's models |
| **provider disabled** | The model's provider is switched off | Activate the provider, or remove the model |
| **model disabled** | The model is inactive in the catalog | Reactivate it in the catalog, or remove it |

## Who can act

Seeing the chains requires `agents:read`. **New Fallback Chain**, the toggle, **Edit**, and **Delete** are enabled only for admins, and the server requires `gateway:manage` for every write.

## Key state to watch

* **With Disabled Model** above zero: at least one chain carries a model the dispatcher cannot use. Open each flagged card and fix or remove the badged model.
* A chain whose first entry is badged: its highest-priority model is unusable, so fix that entry first.
* **Active** lower than **Total Chains**: some chains are switched off; confirm that is intended.
* An empty page ("No fallback chains yet"): no agent can be assigned a chain, so every agent dispatches from its default model.

## Related surfaces

* [Models](https://docs.gloo.com/forge/console/platform/models)
* [LLM providers](https://docs.gloo.com/forge/console/platform/providers.md)
* [LLM routing](https://docs.gloo.com/forge/console/observe/llm-routing.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.