{"version":"2.1.248","anchor":"background-worker-that-never-starts-is-reported-as-a-crash","canonical_anchor":"background-worker-that-never-starts-is-reported-as-a-crash","heading":"Background worker that never starts is reported as a crash","tier":"notice","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/background-worker-that-never-starts-is-reported-as-a-crash","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Background worker that never starts is reported as a crash\n\nA background worker that dies before starting is reported as a crash, not silence.\n\n**What**\n\nA worker that never became ready and exited for a specific known cause is now classified as crashed rather than passing quietly, so failed background work shows up instead of disappearing.\n\n**Details**\n\n- The new condition sits alongside the existing bad working directory, repeated attempt and last exit cause checks, any of which force the crashed outcome.\n- Feeds the existing `tengu_bg_worker_exit` telemetry.\n\n**Evidence**\n\n`tengu_bg_worker_exit`\n\n- Area: Background Tasks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}