{"version":"2.1.248","anchor":"queued-messages-and-control-frames-now-leave-in-the-order-th","canonical_anchor":"queued-messages-and-control-frames-now-leave-in-the-order-th","heading":"Queued messages and control frames now leave in the order they were produced","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/queued-messages-and-control-frames-now-leave-in-the-order-th","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Queued messages and control frames now leave in the order they were produced\n\nQueued messages and control frames now replay in the order they were made after a reconnect.\n\n**What**\n\nWhile the remote bridge is holding traffic during a flush or reconnect, transcript messages and control frames used to sit in two separate queues and drain one after the other. Every queued item now carries a sequence number and the drain interleaves them, preserving original order.\n\n**Details**\n\n- The two drain log lines were merged into one.\n- No flag; unconditional in this build.\n\n**Evidence**\n\n`queued message(s) and `\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}