{"version":"2.1.323","anchor":"error-reporting-gate-gains-a-no-verdict-state","canonical_anchor":"error-reporting-gate-gains-a-no-verdict-state","heading":"Error reporting check can now end with no verdict","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/error-reporting-gate-gains-a-no-verdict-state","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Error reporting check can now end with no verdict\n\nThe check that decides whether error reporting is allowed now has a separate \"no verdict\" result when it cannot get an answer\n\n**What**\n\nClaude Code checks whether it may send error reports. When that check cannot find an answer, either because nothing is stored or because the lookup has no route, it now records a separate \"no verdict\" result, and error reporting stays blocked.\n\n**Why**\n\nThis changes how Claude Code labels the cases where error reporting is not allowed.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}