{"version":"2.1.273","anchor":"task-status-can-now-report-a-worker-restart-reason","canonical_anchor":"task-status-can-now-report-a-worker-restart-reason","heading":"Task status can now report a worker-restart reason","tier":"notice","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/task-status-can-now-report-a-worker-restart-reason","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Task status can now report a worker-restart reason\n\nBackground tasks can now report they stopped because the worker process restarted\n\n**What**\n\nThe status information for a background task now supports a `reason` field with the value `worker_restart`. It's used when a task is automatically stopped because the underlying worker process restarted and found the task orphaned (left without a running process to resume it) when it came back up. This always appears together with a status of `stopped`, and the same value appears in task stop notifications.\n\n**Why**\n\nThis gives a specific, documented explanation when a background task stops unexpectedly due to the worker restarting, rather than leaving it unclear why the task ended.\n\n- Area: Background Tasks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}