{"version":"2.1.248","anchor":"bridge-reconnect-distinguishes-aborted-from-retry","canonical_anchor":"bridge-reconnect-distinguishes-aborted-from-retry","heading":"Bridge reconnect distinguishes aborted from retry","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/bridge-reconnect-distinguishes-aborted-from-retry","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Bridge reconnect distinguishes aborted from retry\n\nAborted remote reconnects now report as aborted rather than as an ordinary retry.\n\n**What**\n\nWhen a remote bridge session reconnects after re-registering, an aborted signal now reports aborted rather than being folded in with a normal retry, and a rejection reports done.\n\n**Evidence**\n\n`[bridge:poll] reconnectSession(`\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}