{"version":"2.1.248","anchor":"worker-shutdowns-now-carry-a-cause","canonical_anchor":"worker-shutdowns-now-carry-a-cause","heading":"Worker shutdowns now carry a cause","tier":"internal","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/worker-shutdowns-now-carry-a-cause","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Worker shutdowns now carry a cause\n\nBackground workers are now told why they are being stopped, such as a config reload.\n\n**What**\n\nStopping a daemon worker sends a reason along with the shutdown, so a worker can tell an upgrade apart from a config reload. On reload the supervisor passes `\"reload\"` when the worker's session still exists in the new config.\n\n**Details**\n\n- Restart now stops every worker first and then starts them back in a staggered sequence, rather than stopping and starting each one in turn.\n\n**Evidence**\n\n`{ type: \"shutdown\", cause: t }`\n\n- Area: Background Tasks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}