{"version":"2.1.317","anchor":"clearer-errors-when-egress-tunnels-are-busy","canonical_anchor":"clearer-errors-when-egress-tunnels-are-busy","heading":"Clearer errors when too many connections go through the outbound proxy at once","tier":"notice","area":"Network","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/clearer-errors-when-egress-tunnels-are-busy","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Clearer errors when too many connections go through the outbound proxy at once\n\nFour new error reasons explain when the proxy for outbound traffic is too busy or refuses connections, and tell you to run fewer downloads at once\n\n**What**\n\nThe egress proxy is the proxy that Claude Code's outbound internet traffic goes through. Claude Code now reports four specific reasons when a connection through it fails:\n\n- `tunnel_wait_timeout`: too many connections were already busy and the wait for a free one ran out\n\n- `tunnel_wait_abandoned`: the wait for a free connection was given up\n\n- `tunnel_queue_full`: the queue of connections waiting for a free one was full\n\n- `ws_open_refused`: the proxy refused new connections with HTTP 429 or 503, which means a rate limit\n\nEach message tells you to run fewer downloads or requests at once.\n\n**Why**\n\nIn remote sessions, these failures used to be hard to explain. Now the message says what went wrong and what to do about it.\n\n- Area: Network\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: both\n- Heads-up: no"}