{"version":"2.1.219","anchor":"armed-fallback-model-must-belong-to-the-same-family","canonical_anchor":"armed-fallback-model-must-belong-to-the-same-family","heading":"Armed fallback model must belong to the same family","tier":"notice","area":"Models","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219\/e\/armed-fallback-model-must-belong-to-the-same-family","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219","markdown":"### Armed fallback model must belong to the same family\n\nFallback model only kicks in when it truly matches the model you asked for.\n\n**What**\n\nThe armed fallback model is only used when it genuinely matches the target, instead of being pushed through a remapping helper first.\n\n**Details**\n\n- The remapping helper call is gone from this path.\n- The fallback is used only when its normalised family matches the mapped target's family and it has not already been tried.\n- Otherwise the code falls through to the regular resolution path.\n\n**Evidence**\n\n`armedFallbackModel`\n\n- Area: Models\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}