{"version":"2.1.225","anchor":"auto-mode-classifier-now-falls-back-when-the-primary-model-r","canonical_anchor":"auto-mode-classifier-now-falls-back-when-the-primary-model-r","heading":"Auto-mode classifier now falls back when the primary model refuses","tier":"soon","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/auto-mode-classifier-now-falls-back-when-the-primary-model-r","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### Auto-mode classifier now falls back when the primary model refuses\n\nWhen the auto-mode model refuses a request, a backup model now gets a try instead of failing.\n\n**What**\n\nA safeguard refusal from the primary classifier model is treated like the model being unavailable, so the fallback model gets a chance instead of the request failing outright. The rollout state of this path could not be resolved in this build.\n\n**Details**\n\n- `refusedBySafeguard` joins unavailability as a trigger for retrying on the fallback model within the remaining time budget\n- Usage and durations from both attempts are merged\n- If the fallback also fails to produce a usable answer, the original result is kept\n- The log line now distinguishes a refusal from an unavailability\n\n**Evidence**\n\n`refused (stop_reason=refusal)`\n\n- Area: Elsewhere\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}