{"version":"2.1.275","anchor":"scheduledautonomous-loop-task-wakeups-can-be-disabled-per-c","canonical_anchor":"scheduledautonomous-loop-task-wakeups-can-be-disabled-per-c","heading":"Scheduled\/autonomous-loop task wakeups can be disabled per component instance","tier":"use","area":"Scheduled Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/scheduledautonomous-loop-task-wakeups-can-be-disabled-per-c","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Scheduled\/autonomous-loop task wakeups can be disabled per component instance\n\nScheduled task wakeups, including \/loop, can now be disabled per component instance\n\n**What**\n\nThe component responsible for scheduled tasks, which handles `\/loop`, cron-style scheduled prompts, and teammate task notifications, now accepts a `disabled` setting. When set, it skips all of its scheduling behavior, including firing handlers, randomized timing jitter, and extra routine cron tasks.\n\n**Why**\n\nThis lets scheduled-task behavior be turned off for a given instance of the component, which is useful in contexts where scheduled wakeups shouldn't run.\n\n- Area: Scheduled Tasks\n- Names: `disabled`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}