Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
Message QueueArea: what it touches
Internal ChangesKind: in v2.1.275,
Internal ChangesSection of the release
What
When session-start hooks abort a batch of queued messages, the non-prompt and "resurrected" messages in that batch are now collected and re-added in reverse order using a new enqueueReportingAdmission call with an {ahead: true} option, instead of being pushed back one at a time with the plain enqueue call used before.
Why
This preserves the original ordering of messages that get put back on the queue after a session-start hook aborts, avoiding messages ending up out of sequence.
