{"version":"2.1.232","anchor":"bridge-reconnect-events-record-re-mint-attempts-and-how-reat","canonical_anchor":"bridge-reconnect-events-record-re-mint-attempts-and-how-reat","heading":"Bridge reconnect events record re-mint attempts and how reattach started","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/bridge-reconnect-events-record-re-mint-attempts-and-how-reat","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Bridge reconnect events record re-mint attempts and how reattach started\n\nRemote bridge reconnects record how many times credentials were re-minted and where a reattach came from.\n\n**What**\n\nRemote bridge websocket events now report how many times credentials were re-minted before connecting, and the event for a reattach that found nothing to attach to records where the reattach came from and whether a revive was initiated.\n\n**Evidence**\n\n`tengu_bridge_repl_ws_connected`\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}