{"version":"2.1.268","anchor":"bridge-teardown-skip-archive-path-now-also-waits-on-a-pref","canonical_anchor":"bridge-teardown-skip-archive-path-now-also-waits-on-a-pref","heading":"Bridge teardown 'skip archive' path now also waits on a preflush hold and reports it","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/bridge-teardown-skip-archive-path-now-also-waits-on-a-pref","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Bridge teardown 'skip archive' path now also waits on a preflush hold and reports it\n\nBridge teardown's skip-archive path now also waits for pending uploads and reports timeouts\n\n**Unclear.** Whether this behavior is active for any given account depends on the tengu_bridge_repl_teardown gate, which is unread for this account, so nothing can be said about whether it is switched on.\n\n**What**\n\nWhen a remote bridge session tears down and skips archiving, it now waits on a pending-uploads check if there are uploads still in flight, and logs a new failure reason, `skip_archive_flush_timeout`, if that wait doesn't finish in time. The teardown telemetry now also includes the fields `hold_preflush_ms` and `hold_preflush_landed` on this skip-archive path, which previously only recorded them on the full-archive path.\n\n**Why**\n\nThis brings the skip-archive teardown path in line with the full-archive path, so timing and success information about the pre-teardown upload flush is captured consistently regardless of which teardown path runs.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}