{"version":"2.1.290","anchor":"lost-session-timers-reported-to-claude-after-a-container-res","canonical_anchor":"lost-session-timers-reported-to-claude-after-a-container-res","heading":"Claude is told which timers were lost when a remote session's container restarts","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/lost-session-timers-reported-to-claude-after-a-container-res","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Claude is told which timers were lost when a remote session's container restarts\n\nAfter a container restart, Claude Code lists the scheduled timers that did not survive and asks Claude to set each one up again\n\n**Unclear.** What triggers this check, and whether a switch controls it, is not clear.\n\n**What**\n\nA remote session runs inside a container, an isolated computer environment. Timers, such as scheduled tasks and wake-up reminders, do not survive when that container restarts. Claude Code now looks for timers lost this way, tells Claude which ones are gone and will not fire, and asks it to reschedule each one.\n\n**Why**\n\nScheduled work in remote sessions is no longer lost without anyone noticing when the container restarts.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}