{"version":"2.1.238","anchor":"idle-spare-sessions-clear-their-marker-once-they-get-work","canonical_anchor":"idle-spare-sessions-clear-their-marker-once-they-get-work","heading":"Idle spare sessions clear their marker once they get work","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/idle-spare-sessions-clear-their-marker-once-they-get-work","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Idle spare sessions clear their marker once they get work\n\nA pre-warmed spare session now clears its spare marker once real work arrives.\n\n**What**\n\nA session started as a spare now clears its spare flag in its process file when it becomes busy, and a poll clears it when a session state file appears in the session directory.\n\n**Details**\n\n- Only sessions marked as born spare are affected.\n- The process-file writer now returns whether the write succeeded instead of discarding the result, and logs `[concurrentSessions] updatePidFile failed:` when it does not.\n\n**Evidence**\n\n`[concurrentSessions] updatePidFile failed:`\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5"}