{"version":"2.1.275","anchor":"scheduled-task-lock-acquisition-skipped-in-certain-remoteso","canonical_anchor":"scheduled-task-lock-acquisition-skipped-in-certain-remoteso","heading":"Scheduled task lock acquisition skipped in certain remote\/So() sessions","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/scheduled-task-lock-acquisition-skipped-in-certain-remoteso","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Scheduled task lock acquisition skipped in certain remote\/So() sessions\n\nA scheduled-task lock is now skipped entirely in certain remote sessions instead of being acquired\n\n**Unclear.** It is unclear exactly what session\/context check this guards against or what practical effect skipping the lock has for the reader.\n\n**What**\n\nThe internal function that acquires a lock before running a scheduled task now returns immediately, without ever touching the lock file, when no explicit lock directory is given and the session is running in a certain remote context. In that situation the lock is simply never acquired.\n\n**Why**\n\nSkipping the lock check avoids unnecessary file operations in remote sessions where the lock wasn't being used meaningfully, though it means scheduled-task locking behaves differently there than in a normal local session.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}