{"version":"2.1.239","anchor":"requesting-a-model-you-are-not-permitted-to-use-can-now-step","canonical_anchor":"requesting-a-model-you-are-not-permitted-to-use-can-now-step","heading":"Requesting a model you are not permitted to use can now step down instead of failing","tier":"notice","area":"Models","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/requesting-a-model-you-are-not-permitted-to-use-can-now-step","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Requesting a model you are not permitted to use can now step down instead of failing\n\nSwitching to a model you aren't allowed to use now falls back to a substitute instead of failing.\n\n**What**\n\nWhen a program switches models mid-session through the control channel, a name that is recognized but not permitted no longer just gets blocked; a substitute model is picked instead.\n\n**Details**\n\n- The requested name is classified as default, unrecognized, allowed, blocked or stepped down.\n- An unrecognized name still returns the shape it expected plus a suggestion, and is reported as `tengu_set_model_unrecognized`.\n\n**Evidence**\n\n`steppedDown`\n\n- Area: Models\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}