{"version":"2.1.290","anchor":"resume-of-background-crons-carries-them-forward","canonical_anchor":"resume-of-background-crons-carries-them-forward","heading":"Background task scan can carry scheduled jobs forward","tier":"notice","area":"Scheduled Tasks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/resume-of-background-crons-carries-them-forward","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Background task scan can carry scheduled jobs forward\n\nThe background task scan can now carry over scheduled cron jobs as temporary entries that are not saved, and the task notification text changed\n\n**Unclear.** It is not known what passes the carried jobs to the scan, so when this happens in practice is unclear.\n\n**What**\n\nA cron job is a task set to run on a schedule. Claude Code's scan of background tasks can now take a list of cron jobs to carry over. For each one, it creates an entry whose id begins with \"carried:\". These entries are marked as not durable, meaning they are not saved to last beyond the current run. The wording of the notification about background tasks also changed.\n\n**Why**\n\nScheduled jobs from an earlier conversation may survive when you resume a session or when Claude Code compacts it. Compacting means shortening the conversation history so it fits.\n\n- Area: Scheduled Tasks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}