{"version":"2.1.219","anchor":"teleport-repo-mismatch-telemetry-records-where-the-check-ran","canonical_anchor":"teleport-repo-mismatch-telemetry-records-where-the-check-ran","heading":"Teleport repo-mismatch telemetry records where the check ran","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219\/e\/teleport-repo-mismatch-telemetry-records-where-the-check-ran","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219","markdown":"### Teleport repo-mismatch telemetry records where the check ran\n\nRepo-mismatch warnings now record which check caught the problem, for diagnosis.\n\n**What**\n\nRepo mismatch and not-in-repo teleport events now say which code path detected the problem.\n\n**Details**\n\n- New `stage` field: `resume_validate` on the resume path, `direct_arg_detect` when detected from the direct argument.\n- The mismatch display strings are now produced by a shared helper rather than built at each site.\n\n**Evidence**\n\n`direct_arg_detect`\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}