{"version":"2.1.311","anchor":"gateway-failed-upstream-responses-carry-x-gateway-model-an","canonical_anchor":"gateway-failed-upstream-responses-carry-x-gateway-model-an","heading":"Gateway error responses now say which model was tried","tier":"notice","area":"Gateway","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/gateway-failed-upstream-responses-carry-x-gateway-model-an","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Gateway error responses now say which model was tried\n\nWhen every upstream fails, the gateway's 499 and 502 responses now carry an x-gateway-model header, and 502s copy some upstream headers\n\n**What**\n\nWhen the gateway in Claude Code cannot get a working answer from any of the servers behind it, it replies with a 499 or 502 error. Those responses now include an `x-gateway-model` header. A 502 response also copies some headers from the last server that failed. Before, these responses carried no extra headers.\n\n**Why**\n\nAnyone running the gateway gets more to go on when working out why every server failed.\n\n- Area: Gateway\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: org\n- Heads-up: no"}