{"version":"2.1.323","anchor":"scheduler-lock-release-checks-the-owner-and-live-process","canonical_anchor":"scheduler-lock-release-checks-the-owner-and-live-process","heading":"One session can no longer release another session's scheduled-task lock","tier":"notice","area":"Scheduled Tasks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/scheduler-lock-release-checks-the-owner-and-live-process","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### One session can no longer release another session's scheduled-task lock\n\nReleasing the scheduled-tasks lock now needs the owner's key and is skipped while another running process still holds it\n\n**What**\n\nClaude Code uses a lock so that only one session runs scheduled tasks at a time. Releasing that lock now needs the owner's key, and Claude Code does not release it if a different process that is still running holds it. Before, the lock was released whenever the session ID matched.\n\n**Why**\n\nOne session can no longer drop a lock that another session is still using, so scheduled tasks are less likely to be run twice or left without an owner.\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"}