{"version":"2.1.290","anchor":"restart-notice-now-covers-lost-timers","canonical_anchor":"restart-notice-now-covers-lost-timers","heading":"Restart notice now mentions timers that will not fire","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/restart-notice-now-covers-lost-timers","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Restart notice now mentions timers that will not fire\n\nAfter a container restart, the notice about lost background work now also lists pending timers that will not fire\n\n**Unclear.** It is not clear which kinds of timers are counted in this list.\n\n**What**\n\nSome sessions run inside a container, an isolated environment that can be restarted. After a restart, Claude Code tells Claude which background tasks were lost. That notice now also says that timers which were pending in that container will not fire either.\n\n**Why**\n\nClaude is told to set those timers up again, so scheduled follow-ups are less likely to be silently forgotten after a restart.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}