{"version":"2.1.290","anchor":"session-cron-resurrection-reworked","canonical_anchor":"session-cron-resurrection-reworked","heading":"Scheduled session tasks are restored differently when you resume","tier":"internal","area":"Scheduled Tasks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/session-cron-resurrection-reworked","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Scheduled session tasks are restored differently when you resume\n\nResuming now hands back the scheduled tasks to restore and records when recurring ones last ran, instead of restarting them itself\n\n**Unclear.** The code that receives the returned tasks was not examined, so how they are restarted is not confirmed.\n\n**What**\n\nA session is one conversation with Claude Code, and it can have scheduled tasks that run on a timer. When you resume a session, the step that brings those tasks back no longer registers them itself. It now returns the list of tasks to restore, and for recurring tasks it adds `lastFiredAt`, the time the task last ran.\n\n**Why**\n\nBecause the last run time is kept, recurring tasks may not run straight away after you resume a session.\n\n- Area: Scheduled Tasks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}