{"version":"2.1.265","anchor":"diagnostics-no-row-message-now-covers-older-page-case","canonical_anchor":"diagnostics-no-row-message-now-covers-older-page-case","heading":"Diagnostics \"no row\" message now covers older-page case","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/diagnostics-no-row-message-now-covers-older-page-case","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Diagnostics \"no row\" message now covers older-page case\n\nDiagnostics \"no data\" message now also explains an older page can't capture diagnostics\n\n**What**\n\nThe verify-diagnostics screen's message for when no diagnostic row is found now adds another possible reason: the page you're on may be an older version that can't capture diagnostics at all. This is in addition to the existing reasons (older than 24 hours, or not readable).\n\n**Why**\n\nThis gives a clearer explanation when diagnostics are missing, so you're not left guessing whether it's a timing issue, a permissions issue, or simply an outdated page.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}