{"version":"2.1.267","anchor":"snooze-like-entries-nameuntil-now-scoped-by-sessionid","canonical_anchor":"snooze-like-entries-nameuntil-now-scoped-by-sessionid","heading":"\"snooze\"-like entries (name\/until) now scoped by sessionId","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/snooze-like-entries-nameuntil-now-scoped-by-sessionid","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### \"snooze\"-like entries (name\/until) now scoped by sessionId\n\nSnooze-style entries (name\/until) can now be scoped to a specific session\n\n**Unclear.** What feature actually creates or reads these session-scoped snooze entries is not stated.\n\n**What**\n\nInternal \"snooze\" entries, which pair a `name` with an `until` time, can now also carry an optional `sessionId`. Both the validator that checks these entries and the code that redacts them before logging now accept and pass through this field.\n\n**Why**\n\nScoping these entries by session means the same name\/until pattern can apply differently depending on which session it belongs to, rather than being treated as global.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}