{"version":"2.1.224","anchor":"bridge-websocket-closes-record-why","canonical_anchor":"bridge-websocket-closes-record-why","heading":"Bridge websocket closes record why","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/bridge-websocket-closes-record-why","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Bridge websocket closes record why\n\nRemote bridge socket closes now record a cause alongside the numeric code.\n\n**What**\n\nThe close event for the v2 remote bridge transport now carries a cause alongside the numeric close code, and the deferred-close path stores both.\n\n**Evidence**\n\n`tengu_bridge_repl_ws_closed`\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}