{"version":"2.1.265","anchor":"remote-bridge-teardown-now-records-whether-the-pre-teardown","canonical_anchor":"remote-bridge-teardown-now-records-whether-the-pre-teardown","heading":"Remote bridge teardown now records whether the pre-teardown upload flush completed vs timed out","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/remote-bridge-teardown-now-records-whether-the-pre-teardown","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Remote bridge teardown now records whether the pre-teardown upload flush completed vs timed out\n\nRemote bridge session teardown now logs whether the pre-teardown data upload finished in time\n\n**Unclear.** Nothing has been read yet about the `tengu_bridge_repl_teardown` gate for this release, so no statement can be made about whether this reporting is active for any account.\n\n**What**\n\nWhen a remote bridge session (used for remote control of a session) is torn down, the `tengu_bridge_repl_teardown` telemetry event now records additional details: whether the flush that uploads pending data before teardown completed before its deadline (`hold_preflush_landed`), the computed budget allowed for archiving, and how long the archive upload call actually took.\n\n**Why**\n\nThis gives more detail for diagnosing whether session data was fully saved before a remote session ended, and how long that process took, building on earlier changes that distinguished different kinds of skipped cleanup during teardown.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}