{"version":"2.1.248","anchor":"a-worker-that-never-starts-is-reported-as-a-start-failure-no","canonical_anchor":"a-worker-that-never-starts-is-reported-as-a-start-failure-no","heading":"A worker that never starts is reported as a start failure, not a timeout","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/a-worker-that-never-starts-is-reported-as-a-start-failure-no","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### A worker that never starts is reported as a start failure, not a timeout\n\nA background worker that never starts is named as a start failure instead of hanging until timeout.\n\n**What**\n\nWhen a background worker fails to launch, the failure is now recorded instead of leaving a gap. The sync journal that a cloud session writes for the laptop side can mark itself halted with a reason and the line involved, and a placeholder transcript record is produced in its place, so the laptop names the worker that never came up rather than waiting for a timeout.\n\n**Details**\n\n- the placeholder transcript record is marked halted with reason `start_failed` and attributed to the worker side\n- the journal halt entry carries both the reason and the line involved\n- a decoder for the start-failed case lets the laptop read these entries and surface them\n\n**Evidence**\n\n`decodeWorkerStartFailed`, `start_failed`\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}