{"version":"2.1.228","anchor":"bridge-teardown-records-why-a-session-was-abandoned","canonical_anchor":"bridge-teardown-records-why-a-session-was-abandoned","heading":"Bridge teardown records why a session was abandoned","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/bridge-teardown-records-why-a-session-was-abandoned","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Bridge teardown records why a session was abandoned\n\nGiving up on a remote bridge session after a fatal reconnect is now recorded with that reason.\n\n**What**\n\nWhen a remote bridge session fails fatally during reconnect, the abandonment is now recorded with the reason `abandoned_after_fatal_reconnect` before the connection is cleared and the error is printed.\n\n**Evidence**\n\n`abandoned_after_fatal_reconnect`\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}