{"version":"2.1.314","anchor":"cron-scheduler-skipped-when-an-extra-check-passes-in-headles","canonical_anchor":"cron-scheduler-skipped-when-an-extra-check-passes-in-headles","heading":"Scheduled tasks can be skipped in headless and remote runs","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/cron-scheduler-skipped-when-an-extra-check-passes-in-headles","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Scheduled tasks can be skipped in headless and remote runs\n\nIn headless and remote runs, the scheduler for timed tasks no longer starts when a new check passes\n\n**Unclear.** What the new check tests is not known, so it is unclear which sessions lose their scheduled tasks.\n\n**What**\n\nWhen Claude Code runs without its interactive screen, for example from a script or remotely, it can start a scheduler that runs tasks at set times. It used to start that scheduler whenever scheduled tasks were enabled. It now also requires a new check to come back false. When that check passes, the scheduler does not start.\n\n**Why**\n\nIn some sessions, scheduled tasks may not run, and nothing will say so. If a timed task does not fire in a headless or remote run, this is a place to look.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}