{"version":"2.1.225","anchor":"bridge-teardown-distinguishes-a-skipped-re-mint-loop-from-a-","canonical_anchor":"bridge-teardown-distinguishes-a-skipped-re-mint-loop-from-a-","heading":"Bridge teardown distinguishes a skipped re-mint loop from a skipped teleport","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/bridge-teardown-distinguishes-a-skipped-re-mint-loop-from-a-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### Bridge teardown distinguishes a skipped re-mint loop from a skipped teleport\n\nSession teardown reporting now distinguishes two different kinds of skipped cleanup.\n\n**What**\n\nThe bridge teardown telemetry event can now say which of two skips happened when a session is torn down.\n\n**Details**\n\n- `tengu_bridge_repl_teardown` gains `archive_status` value `skipped_remint_loop`, alongside the existing `skipped_teleport`.\n- Reported when the teardown reason is something other than `remote_control_disabled`.\n- The value is new in this build.\n\n**Evidence**\n\n`skipped_remint_loop`\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}