{"version":"2.1.222","anchor":"bridge-connect-timeouts-are-classified-for-recovery-reportin","canonical_anchor":"bridge-connect-timeouts-are-classified-for-recovery-reportin","heading":"Bridge connect timeouts are classified for recovery reporting","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222\/e\/bridge-connect-timeouts-are-classified-for-recovery-reportin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222","markdown":"### Bridge connect timeouts are classified for recovery reporting\n\nRemote connection timeouts now record whether they happened during recovery or a token refresh.\n\n**What**\n\nA repl-bridge connect timeout now records which path triggered the attempt, so timeouts during recovery can be told apart from those during a token refresh.\n\n**Details**\n\n- recovery_connect_timeout is used for the auth-401, init-4091, and heartbeat-4093 recovery paths.\n- refresh_connect_timeout is used for a proactive token refresh.\n- The existing tengu_bridge_repl_connect_timeout event still fires.\n\n**Evidence**\n\n`recovery_connect_timeout`\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}