{"version":"2.1.319","anchor":"relay-http-status-to-error-reason-map-added","canonical_anchor":"relay-http-status-to-error-reason-map-added","heading":"Relay errors now map to named reasons, with a message for unsent files","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/relay-http-status-to-error-reason-map-added","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Relay errors now map to named reasons, with a message for unsent files\n\nHTTP errors from the relay now map to named reasons such as relay_busy, and a message reports files a connector upload refused\n\n**What**\n\nWhen the relay answers with an HTTP error code, Claude Code now turns that code into a named reason:\n\n- 404 becomes address_used_or_gone\n\n- 429 and 503 become relay_busy\n\n- 504 becomes partner_too_slow\n\nThere is also a message for when a file is not sent because the upload address in a connector's answer was refused. A connector is an outside service Claude Code can reach.\n\n**Why**\n\nThese point to error handling for the relay and for sending files through connectors.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}