{"version":"2.1.285","anchor":"bridge-init-retry-uses-a-shared-backoff-helper","canonical_anchor":"bridge-init-retry-uses-a-shared-backoff-helper","heading":"Remote connection setup retries now use shared timing with random spread","tier":"internal","area":"Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/bridge-init-retry-uses-a-shared-backoff-helper","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Remote connection setup retries now use shared timing with random spread\n\nWhen setting up a remote connection fails, the wait before retrying is now worked out by shared code with 25% random variation\n\n**Unclear.** Whether the actual waits differ from before is not clear.\n\n**What**\n\nWhen Claude Code fails to set up its remote connection, it waits and tries again, waiting longer after each failure. That wait is now worked out by shared code that adds random variation of up to 25% either way. It is still capped by the maximum retry delay setting. Before, the wait was calculated separately in this one place.\n\n**Why**\n\nIn practice this is a minor change to how long retries wait. Random variation spreads retries out so many clients do not all try again at the same moment.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}