{"version":"2.1.309","anchor":"tool-results-distinguish-errors-from-tools-that-never-starte","canonical_anchor":"tool-results-distinguish-errors-from-tools-that-never-starte","heading":"Usage data now tells failed tools apart from tools that never started","tier":"internal","area":"Telemetry","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/tool-results-distinguish-errors-from-tools-that-never-starte","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Usage data now tells failed tools apart from tools that never started\n\nClaude Code's usage data now separates tool errors where the tool never started in this process from other errors\n\n**What**\n\nIn the usage data Claude Code reports about tool results, an error from a tool that never started in the current process is now recorded as its own kind. Before, it was recorded the same as any other error.\n\n**Why**\n\nThis affects only the reported data and changes nothing you see.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}