A remote bridge that cannot recover now stops retrying after a budget and tells you why.
What's wrong with this entry?
Recovery from 401, 4091 and 4093 transport closes is now table-driven, and repeated transport rebuilds are capped so a bridge that cannot heal stops retrying and says why.
- each close code maps to its own reconnect detail, cause, diagnostic, terminal-vs-retry fetch failure classification and recovered code
- 4093 rebuilds within a one hour window are budgeted; exceeding the budget stops recovery with an explicit message
- new presence telemetry codes: recovery_exhausted, heartbeat_budget_exhausted, recovery_no_oauth_token, recovery_reauth_required, recovery_credentials_fetch_failed, recovery_credentials_rejected, recovery_abandoned_at_teardown, bridge_connect_died_before_presence
presence heartbeats to the server kept failing after repeated reconnects
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Remote bridge replaces stale-epoch recovery with a one-shot supersession close
Both mention bridge
-
v2.1.236
Remote bridge waits for the disconnect notice, and an inbox fetch that is always off
Both mention bridge
-
v2.1.236
Bridge shuts down cleanly on SIGHUP
Both mention bridge