{"version":"2.1.232","anchor":"auto-mode-setup-picks-its-own-model-and-retries-on-a-fallbac","canonical_anchor":"auto-mode-setup-picks-its-own-model-and-retries-on-a-fallbac","heading":"Auto-mode setup picks its own model and retries on a fallback","tier":"notice","area":"Auto Mode","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/auto-mode-setup-picks-its-own-model-and-retries-on-a-fallbac","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Auto-mode setup picks its own model and retries on a fallback\n\nAuto-mode setup picks its own scan model, retries a fallback, and names the failure.\n\n**What**\n\nThe setup scan no longer takes a model from its caller; it resolves one from the auto-mode configuration. If none resolves, it fails with the new code `no_model` and tells you \"No model is available for the scan in this session\u2019s auto-mode configuration.\" If the call fails outright, it now retries once on a fallback model.\n\n**Details**\n\n- The retry logs \"auto-mode-setup propose: primary model failed; retrying on fallback\" and only happens for `api_failed` results that were not aborted.\n- A successful retry is recorded as outcome `model_fell_back` on the `auto_mode_setup_propose` event; the missing-model case is recorded as `no_model`.\n\n**Evidence**\n\n`auto-mode-setup propose: primary model failed; retrying on fallback`, `No model is available for the scan in this session\u2019s auto-mode configuration.`\n\n- Area: Auto Mode\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}