{"version":"2.1.228","anchor":"bridge-reconnects-re-register-after-a-conflict-up-to-a-limit","canonical_anchor":"bridge-reconnects-re-register-after-a-conflict-up-to-a-limit","heading":"Bridge reconnects re-register after a conflict, up to a limit","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/bridge-reconnects-re-register-after-a-conflict-up-to-a-limit","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Bridge reconnects re-register after a conflict, up to a limit\n\nAfter a network drop, sessions re-register automatically, but only a limited number of times per hour.\n\n**What**\n\nAfter a network interruption, a bridge session that comes back to a conflict now re-registers instead of giving up, but no more than a fixed number of times per hour. Past that it stops with an explicit message.\n\n**Details**\n\n- Worker registration uses compare-and-swap fencing so a stale connection cannot overwrite a newer one.\n- If another connection has genuinely taken the session over, this device stands down and says so rather than retrying.\n\n**Evidence**\n\n`another connection took over this session while it was being restored \\u2014 this device is standing down`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}