{"version":"2.1.323","anchor":"scheduled-tasks-file-read-failure-no-longer-treated-as-empty","canonical_anchor":"scheduled-tasks-file-read-failure-no-longer-treated-as-empty","heading":"A damaged scheduled tasks file is no longer wiped when you remove a task","tier":"notice","area":"Scheduled Tasks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/scheduled-tasks-file-read-failure-no-longer-treated-as-empty","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### A damaged scheduled tasks file is no longer wiped when you remove a task\n\nIf `.claude\/scheduled_tasks.json` cannot be read, removing a task now stops with a message instead of treating the file as empty\n\n**What**\n\nScheduled tasks are kept in the file `.claude\/scheduled_tasks.json`. Before, if that file could not be read or was malformed, Claude Code treated it as an empty list, so removing a task could overwrite the file and lose every task in it.\n\nNow:\n\n- An unreadable or malformed file is reported as unreadable.\n\n- Removing a task then does nothing and asks you to check or repair the file and try again.\n\n- Adding a task can replace an existing task with the same id.\n\n**Why**\n\nA single damaged file no longer leads to all your scheduled tasks being deleted.\n\n- Area: Scheduled Tasks\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}