{"version":"2.1.321","anchor":"fatal-exit-paths-now-carry-a-cause","canonical_anchor":"fatal-exit-paths-now-carry-a-cause","heading":"Crash and forced exits now record a specific cause","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/fatal-exit-paths-now-carry-a-cause","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Crash and forced exits now record a specific cause\n\nClaude Code now records a specific cause, such as an uncaught error or a failed worker registration, when it shuts down abnormally\n\n**What**\n\nWhen Claude Code shuts down because something went wrong, it now records a cause along with the shutdown. Causes include:\n\n- `uncaught_exception`: an error nothing caught\n\n- `repeated_uncaught_exceptions`: several such errors\n\n- `worker_registration_failed`: a background worker could not register\n\n- `resume_message_not_found`: a message needed to resume could not be found\n\n- `sandbox_required_unavailable`: a required sandbox could not run\n\nFor these exits, the general shutdown reason is \"other\".\n\n**Why**\n\nDifferent kinds of crash and forced exit can now be told apart when looking into what went wrong.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}