# Chat messages being processed out of order

**URL:** <https://meta.discourse.org/t/chat-messages-being-processed-out-of-order/388770>\
**Category:** Bug\
**Tags:** chat\
**Created:** [November 18, 2025, 3:08am UTC](https://meta.discourse.org/t/chat-messages-being-processed-out-of-order/388770 "2025-11-18T03:08:35Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![j.jaffeux](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/j.jaffeux/32/60297_2.png) [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)\
**Post date:** [October 13, 2026, 7:42am UTC](https://meta.discourse.org/t/chat-messages-being-processed-out-of-order/388770/10 "2026-10-13T07:42:04Z")

</div>

That should fix it

> <https://github.com/discourse/discourse/pull/44035>
>
> Previously, chat saved the sender's device clock as the message \`created\_at\` (#3…4592). Users with a skewed clock had all their messages shifted for everyone, so replies could show above the message they answered (\[meta\](https://meta.discourse.org/t/388770)), and the \`id\` pagination cursor skipped those messages.
> 
> This change always uses the server time and keeps staged messages after confirmed ones on the client, instead of comparing the two clocks. \`Chat::MessagesQuery\` now pages on \`(created\_at, id)\`, so messages already stored with a skewed time load again.

---

_[View the full topic](https://meta.discourse.org/t/chat-messages-being-processed-out-of-order/388770)._
