{"version":"2.1.257","anchor":"new-telemetry-for-unrecognizedunserved-model-spellings-at-s","canonical_anchor":"new-telemetry-for-unrecognizedunserved-model-spellings-at-s","heading":"New telemetry for unrecognized\/unserved model spellings at startup","tier":"internal","area":"Models","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/new-telemetry-for-unrecognizedunserved-model-spellings-at-s","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### New telemetry for unrecognized\/unserved model spellings at startup\n\nStartup now reports when an org's default model name is unrecognized or a requested family spelling went unserved.\n\nStartup model resolution now tracks two new conditions: whether the org's default model name is unrecognized, and whether a \"family spelling\" requested by the user went unserved (`family_spelling_unserved`). Both are now reported as telemetry outcomes.\n\n- Area: Models\n- Names: `family_spelling_unserved`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}