{"version":"2.1.225","anchor":"bridge-auth-failures-no-longer-burn-reconnect-attempts","canonical_anchor":"bridge-auth-failures-no-longer-burn-reconnect-attempts","heading":"Bridge auth failures no longer burn reconnect attempts","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/bridge-auth-failures-no-longer-burn-reconnect-attempts","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### Bridge auth failures no longer burn reconnect attempts\n\nA login problem on the bridge no longer eats your reconnect attempts and is now named clearly.\n\n**What**\n\nAn authentication failure in the repl-bridge connect loop is reported as such and does not consume one of the limited retries.\n\n**Details**\n\n- the retry counter is incremented only for non-auth failures\n- failures now carry an explicit kind: `auth` for auth failures, `terminal` otherwise\n- replaces a single generic terminal path for both cases\n\n**Evidence**\n\n`auth`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}