{"version":"2.1.317","anchor":"idle-connection-recycling-for-model-api-and-sessions-server","canonical_anchor":"idle-connection-recycling-for-model-api-and-sessions-server","heading":"Claude Code opens fresh server connections after errors or timeouts","tier":"notice","area":"Network","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/idle-connection-recycling-for-model-api-and-sessions-server","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Claude Code opens fresh server connections after errors or timeouts\n\nAfter certain error responses, or a request that gets no reply in time, Claude Code drops its idle connections to that server and opens new ones\n\n**What**\n\nWhen a request to the model API (the service that runs Claude) or to Anthropic's sessions server comes back with certain error statuses, or gets no answer in time, Claude Code now closes its idle connections to that server and opens new ones. A connection here is an open link to a server that Claude Code keeps so later requests can reuse it. An idle one is a connection not in use at that moment.\n\nClaude Code writes a note in its debug log when it does this. It only happens under certain internal conditions that Claude Code checks for itself.\n\n**Why**\n\nA connection that has gone bad can keep causing failures if it is reused. Starting fresh after an error or a hang should help a session recover on its own instead of running into the same problem again.\n\n- Area: Network\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}