{"version":"2.1.275","anchor":"message-re-queue-after-aborted-session-start-hooks-now-prese","canonical_anchor":"message-re-queue-after-aborted-session-start-hooks-now-prese","heading":"Message re-queue after aborted session-start hooks now preserves order via enqueueReportingAdmission","tier":"internal","area":"Message Queue","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/message-re-queue-after-aborted-session-start-hooks-now-prese","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Message re-queue after aborted session-start hooks now preserves order via enqueueReportingAdmission\n\nRe-queued messages after an aborted session-start hook now keep their original order\n\n**What**\n\nWhen 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.\n\n**Why**\n\nThis 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.\n\n- Area: Message Queue\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}