{"version":"2.1.281","anchor":"scheduled-tasks-survive-a-throwing-fire-handler","canonical_anchor":"scheduled-tasks-survive-a-throwing-fire-handler","heading":"Scheduled tasks survive a throwing fire handler","tier":"notice","area":"Scheduled Tasks","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/scheduled-tasks-survive-a-throwing-fire-handler","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Scheduled tasks survive a throwing fire handler\n\nA scheduled task whose run fails with an error no longer disrupts scheduling: one-off tasks stay saved and recurring runs are skipped\n\n**What**\n\nStarting a scheduled task, or one that was missed earlier, is now protected against errors. If the code that runs it fails:\n\n- A one-off task stays in `scheduled_tasks.json` so a later session can run it.\n\n- That run of a recurring task is dropped and not retried.\n\nThe error is reported with any text you typed removed.\n\n**Why**\n\nOne failing task no longer takes scheduling down with it. A one-off task you set up is kept, not lost.\n\n- Area: Scheduled Tasks\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}