{"version":"2.1.323","anchor":"scheduled-task-lock-ownership-now-tracked-by-owner-key","canonical_anchor":"scheduled-task-lock-ownership-now-tracked-by-owner-key","heading":"The scheduled-task lock now records which session owns it","tier":"notice","area":"Scheduled Tasks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/scheduled-task-lock-ownership-now-tracked-by-owner-key","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### The scheduled-task lock now records which session owns it\n\nThe lock that stops scheduled tasks from running twice now records the owning session, and is rewritten when the owner is unclear\n\n**Unclear.** What this fixes for scheduled tasks in practice is not stated.\n\n**What**\n\nScheduled tasks use a lock so that only one Claude Code process runs them at a time. When a process takes the lock, it now records its session ID as the owner. The lock is rewritten when it belongs to a different process or has no owner recorded. Before, the check compared against the wrong value.\n\n**Why**\n\nThis may fix how scheduled tasks share the lock between several Claude Code processes.\n\n- Area: Scheduled Tasks\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}