{"version":"2.1.283","anchor":"daemon-supervisor-logs-worker-kinds-that-are-unavailable-for","canonical_anchor":"daemon-supervisor-logs-worker-kinds-that-are-unavailable-for","heading":"Background workers not available for your account are now logged and can start later","tier":"notice","area":"Background Daemon","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/daemon-supervisor-logs-worker-kinds-that-are-unavailable-for","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Background workers not available for your account are now logged and can start later\n\nThe daemon now logs worker kinds it will not start for your account, and starts them if they become available when flags refresh\n\n**Unclear.** It is not clear which flags decide whether each worker kind is available.\n\n**What**\n\nThe daemon is a background process that runs workers, which are long-running jobs you configure. At startup it used to skip workers of a kind not enabled for your account without saying anything. It now logs \"not starting N worker(s): not available for this account\", once for each kind.\n\nIt also rechecks when feature flags (settings the server sends to switch features on) refresh. If a worker kind becomes available while the daemon is running, those workers start without you reloading the config.\n\n**Why**\n\nConfigured workers that never appeared used to give no explanation. The log line now says why, and a newly available kind no longer needs a restart or config reload.\n\n- Area: Background Daemon\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}