{"version":"2.1.197","anchor":"explicit-error-for-missing-bedrock-fallback-id","canonical_anchor":"explicit-error-for-missing-bedrock-fallback-id","heading":"Explicit Error for Missing Bedrock Fallback ID","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.197\/e\/explicit-error-for-missing-bedrock-fallback-id","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.197","markdown":"### Explicit Error for Missing Bedrock Fallback ID\n\n**What**\n\nThe function that resolves default 3rd-party model IDs now throws a descriptive error if a model tier is configured with `bedrock: null`, instead of silently passing `null` downstream.\n\n**Details**\n\n- Previous behavior: `null` was passed as the Bedrock fallback ID, which could produce cryptic downstream failures\n- New behavior: immediately throws `\"A DEFAULT_3P_*_KEY points at a model config with bedrock: null \u2014 Bedrock setup has no fallback id for that tier\"`\n- This surfaces misconfiguration at the resolution point rather than at API call time\n\n**Evidence**\n\nError message (search for `\"A DEFAULT_3P_*_KEY points at a model config with bedrock: null\"`)"}