{"version":"2.1.257","anchor":"model-switch-disabled-responses-can-now-distinguish-not-off","canonical_anchor":"model-switch-disabled-responses-can-now-distinguish-not-off","heading":"Model-switch-disabled responses can now distinguish 'not offered' from 'disabled by org'","tier":"notice","area":"Models","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/model-switch-disabled-responses-can-now-distinguish-not-off","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### Model-switch-disabled responses can now distinguish 'not offered' from 'disabled by org'\n\nA refused model switch now distinguishes a model that simply is not offered from one disabled by org policy.\n\nModel-switch rejections now check a `notOffered` flag to tell apart two cases: a model that simply isn't offered versus one disabled by org policy. The former now returns a distinct `not_offered` reason and telemetry event, so users get a more accurate explanation for why the switch didn't happen.\n\n- Area: Models\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}