{"version":"2.1.304","anchor":"scheduled-task-missedfire-handlers-can-now-defer-keep-back","canonical_anchor":"scheduled-task-missedfire-handlers-can-now-defer-keep-back","heading":"Missed scheduled tasks can be held back instead of deleted","tier":"internal","area":"Scheduled Tasks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/scheduled-task-missedfire-handlers-can-now-defer-keep-back","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Missed scheduled tasks can be held back instead of deleted\n\nMissed and due scheduled tasks can now be kept back or removed by whatever handles them, instead of being deleted as soon as they are reported\n\n**What**\n\nScheduled tasks are jobs set to run at a given time. When a one-time task is missed, or when a task comes due, the code that handles it now gets more control:\n\n- The handler for missed tasks can keep some of them back, and those are tracked separately for each folder.\n\n- The handler for due tasks can say the task should be kept.\n\n- Both handlers can remove tasks themselves.\n\nBefore, missed tasks were deleted right after they were reported. The log line now says how many missed one-time tasks were reported and how many were kept back.\n\n**Why**\n\nA program running Claude Code can now hold on to tasks until it has dealt with them, so tasks are not lost.\n\n- Area: Scheduled Tasks\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}