{"version":"2.1.222","anchor":"bridge-recovery-has-a-rebuild-budget-and-richer-failure-tele","canonical_anchor":"bridge-recovery-has-a-rebuild-budget-and-richer-failure-tele","heading":"Bridge recovery has a rebuild budget and richer failure telemetry","tier":"notice","area":"Remote Bridge","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222\/e\/bridge-recovery-has-a-rebuild-budget-and-richer-failure-tele","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222","markdown":"### Bridge recovery has a rebuild budget and richer failure telemetry\n\nA remote bridge that cannot recover now stops retrying after a budget and tells you why.\n\n**What**\n\nRecovery 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.\n\n**Details**\n\n- each close code maps to its own reconnect detail, cause, diagnostic, terminal-vs-retry fetch failure classification and recovered code\n- 4093 rebuilds within a one hour window are budgeted; exceeding the budget stops recovery with an explicit message\n- 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\n\n**Evidence**\n\n`presence heartbeats to the server kept failing after repeated reconnects`\n\n- Area: Remote Bridge\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 0\/5"}