# Default model still shows the removed Qwen 3.5 Plus, causing Apps to fail with “no eligible model available”

**URL:** <https://forum.anna.partners/t/default-model-still-shows-the-removed-qwen-3-5-plus-causing-apps-to-fail-with-no-eligible-model-available/324>\
**Category:** Developers\
**Created:** [September 18, 2026, 2:30am UTC](https://forum.anna.partners/t/default-model-still-shows-the-removed-qwen-3-5-plus-causing-apps-to-fail-with-no-eligible-model-available/324 "2026-09-18T02:30:32Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ELFA](https://yyz1.discourse-cdn.com/flex033/user_avatar/forum.anna.partners/elfa/32/22_2.png) [@ELFA](https://forum.anna.partners/u/ELFA)\
**Post date:** [September 18, 2026, 2:30am UTC](https://forum.anna.partners/t/default-model-still-shows-the-removed-qwen-3-5-plus-causing-apps-to-fail-with-no-eligible-model-available/324/1 "2026-09-18T02:30:32Z")

</div>

I found what looks like a model configuration issue.

**Qwen 3.5 Plus** is no longer available in the model list, but for some users, the default Chat model is still showing as **qwen3.5-plus**.

When an App is run with this configuration, it fails with:

> `LLM request failed after 6 attempts: no eligible model available`

For example, in the PPT App, the workflow fails at **Determine presentation language** , and the rest of the process cannot continue.

It looks like:

- Qwen 3.5 Plus has already been removed from the available models.
- Some existing users still have it saved as their default model.
- Apps may still try to use this unavailable model, which results in the “no eligible model available” error.

Could the default model for affected users be automatically migrated to a currently available model when a model is removed?

It may also be worth handling this globally whenever a model is deprecated, so existing users don’t run into App failures because their saved default model is no longer available.

Screenshots attached.

 ![image](https://canada1.discourse-cdn.com/flex033/uploads/anna/original/1X/256db837634a7a1c045b5088dc49967311ff39cd.png)

 ![image](https://canada1.discourse-cdn.com/flex033/uploads/anna/original/1X/241d68a9d72d384fd775b607faf7ae44c61bfb26.jpeg)

 ![image](https://canada1.discourse-cdn.com/flex033/uploads/anna/original/1X/7acb57a8bd02b1611983b52c2e89ac3c4e0f60b9.png)

---

<div class="post-metadata">

**Author:** ![hunter](https://yyz1.discourse-cdn.com/flex033/user_avatar/forum.anna.partners/hunter/32/8_2.png) [@hunter](https://forum.anna.partners/u/hunter)\
**Post date:** [September 20, 2026, 8:39am UTC](https://forum.anna.partners/t/default-model-still-shows-the-removed-qwen-3-5-plus-causing-apps-to-fail-with-no-eligible-model-available/324/2 "2026-09-20T08:39:44Z")

</div>

Hi @ELFA! 👋

Thank you so much for the detailed report — the screenshots and the exact error message made this really easy to track down. This was a great catch! 🙌

**You were spot on.** When Qwen 3.5 Plus was retired from the model catalog, accounts that still had it saved as their default Chat model weren’t migrated. On top of that, the model-selection fallback that should have quietly picked a healthy replacement had a gap, so Apps calling the LLM API could end up with `no eligible model available` instead of a working model. 😿

## ✅ Fixed in `1.1.0-beta.168`

Two improvements shipped:

1. **Resilient model routing** 🛡 — If a saved default model is no longer available, the platform now always falls back to a healthy, currently-available chat model. Apps will never fail with “no eligible model available” as long as any eligible model exists in the catalog.

2. **Automatic migration on deprecation** 🔄 — Exactly what you suggested! Whenever a model is retired from the catalog, affected users’ saved default models are now automatically migrated to a currently available default. This runs as part of every future catalog update, so this class of issue won’t come back. Stale defaults from past removals (including `qwen3.5-plus`) are being migrated as well, so the Settings page will reflect a valid model again.

## What this means for your App 📦

- No changes needed on your side — PPT App workflows (like _Determine presentation language_) will resolve a valid model automatically.
- Affected users don’t need to do anything, though manually re-selecting a model in **Settings → Models** also resolves it instantly.

Thanks again for taking the time to write this up — reports like yours make the platform better for every developer. Keep them coming! 💚

Happy building! 🚀