{"version":"2.1.236","anchor":"idle-notices-queue-behind-earlier-peer-messages","canonical_anchor":"idle-notices-queue-behind-earlier-peer-messages","heading":"Idle notices queue behind earlier peer messages","tier":"notice","area":"Multi-Session","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/idle-notices-queue-behind-earlier-peer-messages","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Idle notices queue behind earlier peer messages\n\nIdle notices from other sessions now wait their turn behind earlier peer messages.\n\n**What**\n\nIdle notifications used to take the fast out-of-band path used by all control messages between sessions; they now go through the ordered processing chain instead, so an idle notice cannot overtake peer messages queued before it.\n\n**Details**\n\n- Only the idle-notice action is excluded from the fast path; other control messages still use it.\n- Reachable when cross-session peer messaging is in use.\n\n**Evidence**\n\n`(e.type === \"control\" && e.action !== \"notify_when_idle\")`\n\n- Area: Multi-Session\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}