{"version":"2.1.246","anchor":"refusal-fallback-metadata-attached-to-requests","canonical_anchor":"refusal-fallback-metadata-attached-to-requests","heading":"Refusal-fallback metadata attached to requests","tier":"soon","area":"Model Routing","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/refusal-fallback-metadata-attached-to-requests","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Refusal-fallback metadata attached to requests\n\nRequests carry fields for a fallback model used after a refusal, with nothing you can set.\n\n**What**\n\nRequests now carry a block of fields describing a fallback used after a model refusal, including the fallback model, its lane, a credit code and mint details, and stamp fields recording the original model, category, trigger and request id. Plumbing for that path; nothing here is user-settable.\n\n**Evidence**\n\n`refusalFallbackModelLane: \"visible\"`\n\n- Area: Model Routing\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 5\/5\n- Present in the build but not switched on"}