{"version":"2.1.314","anchor":"cloud-release-retries-on-network-errors","canonical_anchor":"cloud-release-retries-on-network-errors","heading":"Releasing a remote session now retries after network errors","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/cloud-release-retries-on-network-errors","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Releasing a remote session now retries after network errors\n\nWhen releasing a remote session hits a connection error, Claude Code now retries, waiting 500, 1000 and 2000 milliseconds between attempts\n\n**What**\n\nWhen Claude Code lets go of (releases) a session that runs remotely, a dropped connection such as `ECONNRESET` no longer ends the attempt. Claude Code retries, waiting 500, then 1000, then 2000 milliseconds. If there is still no reply, it reports \"ReleaseSession got no answer\".\n\n**Why**\n\nA brief network problem is less likely to leave a remote session unreleased.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}