> ## Documentation Index > Fetch the complete documentation index at: https://explore.airia.com/llms.txt > Use this file to discover all available pages before exploring further. # Model Deprecation > Understand the warnings Airia shows before a model is retired, when they can no longer be dismissed, and how to move your agents to a supported model. Model providers periodically retire older models. When a model you use is scheduled for retirement, Airia warns you ahead of time with an in-app banner that becomes more prominent as the retirement date approaches — so your agents keep working without interruption. Deprecation dates come from the **model provider**, not from Airia. Airia reads the published retirement date for each model and surfaces a warning while there is still time to act. *** ## Who sees deprecation warnings Deprecation banners are shown to **administrators** and to anyone with permission to manage models. Builders without model-management permissions do not see the banners, because clearing one requires replacing the model. A model only triggers a warning when **both** of these are true: * The model has a published retirement date, and * The model is currently used by **at least one agent**. Models that are deprecated but not used by any agent do not raise a banner — there is nothing to fix. If a model's retirement date is more than 90 days away, no banner appears yet. Airia checks for upcoming retirements **once per day**, so a newly-announced deprecation can take up to a day to surface. *** ## The warning timeline As the retirement date gets closer, Airia escalates the warning through four tiers. The banner appears starting at **90 days** before retirement and updates automatically each day. | Time until retirement | Warning | Can be dismissed? | | ------------------------ | --------------------------- | ----------------------------- | | More than 90 days | No banner yet | — | | 90 days or fewer | Warning banner | Yes (for the current session) | | 60 days or fewer | Warning banner | Yes (for the current session) | | 30 days or fewer | Warning banner | Yes (for the current session) | | **15 days or fewer** | **Critical banner** | **No — cannot be dismissed** | | Past the retirement date | "Already deprecated" banner | No — cannot be dismissed | At **15 days or fewer**, the banner can no longer be dismissed. It stays visible until you move every affected agent to a supported model. This is intentional — it ensures the retirement is not overlooked while there is still time to act. Once the retirement date passes, the banner changes to report that the model **has already been deprecated**. At that point the model may stop responding, and any agent still using it can fail. *** ## Dismissing a warning * **90, 60, and 30-day warnings** can be dismissed. Dismissal lasts for your **current session only** — the banner reappears the next time you sign in, and again each time the warning escalates to the next tier, until the model is replaced. * **The 15-day (and past-due) warning cannot be dismissed.** The only way to clear it is to replace the deprecated model in every agent that uses it. *** ## What the banners look like Airia shows a single banner at the top of the app. The exact wording depends on how many models are affected and how close the retirement date is. **A single model, with time remaining:** Warning! 'GPT-4o' model will be deprecated in 30 days. **View affected agents** **A single model, within 15 days (cannot be dismissed):** Warning! 'GPT-4o' model will be deprecated in 12 days. **View affected agents** **A single model, already retired:** 'GPT-4o' model has been deprecated. **View affected agents** **Several models affected at once (rollup):** Warning! 'GPT-4o' will be deprecated in 12 days. +3 more deprecated models. **View all** When more than one model is affected, Airia combines them into a single rollup banner that shows the most urgent model plus a "+N more" count. The rollup banner is always non-dismissible, and its link opens an overview where you can review and replace every affected model in one place. *** ## In Agent Studio Agent Studio surfaces deprecation directly where you build, so you catch problems on the canvas and when picking a model — not only from the top-of-app banner. ### The model card indicator When an AI Model step on the canvas uses a deprecated (or soon-to-be-deprecated) model, a warning icon appears on the model node. Hovering it explains the situation and offers a one-click replacement: 'GPT-4o' is deprecated and will be removed on May 15, 2026. Replace it before then to avoid disruption. Once the model is past its date, the message changes: 'GPT-4o' has been deprecated and is no longer available. Replace it before publishing this agent. Selecting the icon (or its **Replace Model** action) opens the replacement flow for that model. ### Adding a deprecated model When you add a model to an agent, Airia checks its deprecation status and responds in one of three ways: | Model status | What happens | | ---------------------------------------- | ---------------------------------------------------------------- | | Not deprecated, or more than 90 days out | Added normally — no prompt. | | Deprecated within the next 90 days | **Warning** — you can still add it, or pick a replacement. | | Already past its deprecation date | **Blocked** — it cannot be added; you must choose another model. | **Within 90 days (warning) — you can proceed or swap:** **This model is deprecated.** Select a suggested replacement model or proceed with the deprecated model. **Add anyway** · **Select replacement** **Already deprecated (blocked) — adding is not allowed:** **Model unavailable.** This model has already been deprecated and cannot be added. **Select replacement** The "add a model" check warns starting 90 days before the deprecation date and hard-blocks once the date has passed. This is separate from the top-of-app banner, which escalates through the 90 / 60 / 30 / 15-day tiers described above. ### The deprecated models overview When several models are affected, the rollup banner's **View all** link opens an overview that lists every deprecated model in use, grouped by urgency — **Urgent (≤15 days)**, **Expiring soon (≤30 days)**, and **Scheduled (>30 days)** — alongside each model's deprecation date and the number of agents affected. From here you can replace any model, or bulk-replace one across all of its agents at once. *** ## Resolving a deprecation The action link on the banner takes you to the right place to fix the problem. * For a **single** deprecated model, select **View affected agents** to see every agent that uses it. * For **multiple** deprecated models, select **View all** to open the deprecated models overview. Pick a supported model to take the place of the one being retired. Choose a model with comparable capabilities so your agents continue to behave as expected. Replace the model in each affected agent. From the overview you can **bulk replace** the model across many agents at once. Replacing a model publishes a new version of each affected agent, so review the change before relying on it in production. Once no agents reference the retired model, its banner clears automatically. Don't wait for the 15-day critical banner. Replacing a model creates a new agent version — doing it early, while the warning is still dismissible, gives you time to test the replacement before the old model stops responding. *** ## Related * [Model Lifecycle Management](/building-and-deploying-agents/agent-basics/models) — add, edit, and configure the models available to your agents. * [AI Model Context Settings](/building-and-deploying-agents/agent-basics/ai-model-context) — control what a model sees at runtime.