{"version":"2.1.317","anchor":"proxy-troubleshooting-doc-adds-429503-guidance","canonical_anchor":"proxy-troubleshooting-doc-adds-429503-guidance","heading":"Proxy troubleshooting help now covers 429 and 503 responses","tier":"notice","area":"Network","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/proxy-troubleshooting-doc-adds-429503-guidance","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Proxy troubleshooting help now covers 429 and 503 responses\n\nClaude Code's proxy troubleshooting guidance now covers 429 and 503 responses and suggests running fewer downloads at once\n\n**What**\n\nClaude Code carries guidance on problems with an egress proxy, a server that outgoing network traffic has to pass through. That guidance used to cover only 403 and 407 responses. It now also covers 429 and 503 responses from the proxy, which mean it is turning requests away for now, and suggests running fewer downloads at once.\n\n**Why**\n\nClaude is better placed to recognise a proxy that is throttling requests and to suggest slowing down.\n\n- Area: Network\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: both\n- Heads-up: no"}