{"version":"2.1.248","anchor":"queued-client-events-survive-a-remote-bridge-reconnect","canonical_anchor":"queued-client-events-survive-a-remote-bridge-reconnect","heading":"Queued client events survive a remote bridge reconnect","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/queued-client-events-survive-a-remote-bridge-reconnect","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Queued client events survive a remote bridge reconnect\n\nUndelivered events now carry over when the remote bridge rebuilds its connection.\n\n**What**\n\nWhen the remote bridge rebuilds its connection, for example after refreshing credentials, events that were queued but never delivered are now carried over to the new connection instead of being thrown away. It logs \"[remote-bridge] Carrying N undelivered client event(s) over to the rebuilt transport\". This is unconditional on the bridge path, with no flag to turn it off.\n\n**Details**\n\n- The uploader's close now accepts a retain option, keeping in-flight plus pending items in an undelivered list capped at the same maximum queue size, with take\/peek\/discard accessors.\n- Carry-overs are counted by the telemetry event `tengu_bridge_repl_events_carried_over`; events lost at a terminal failure are counted by `bridge_repl_v2_client_events_lost`.\n- Enqueuing a batch larger than the maximum queue size now splits it into chunks instead of stalling on backpressure.\n\n**Evidence**\n\n`tengu_bridge_repl_events_carried_over`, `retainUndelivered: !0`\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}