I'm having issues sending DMs or channel messages in rapid succession

j.jaffeux · August 27, 2025, 11:26pm

I will experiment with this tomorrow:

github.com/discourse/discourse

FIX: client based chat message timestamp

main ← frontend-timestamp

merged 09:21AM - 28 Aug 25 UTC

jjaffeux

+170 -2

Uses the timestamp at the moment where the user hits send for the created_at val…ue of the chat message. This should ensure very consistent ordering. The implementation is simple: - collects the timestamp and send it in the request (client_created_at) - if client_created_at is present and valid, set it as created_at when creating the message I suspect that we could end up in a situation where a message is routed to a slower worker and even if sent before an other message could end up being persisted later which would cause ordering issues.

And if it goes well, I will merge it later in the week.

Topic		Replies	Views
Chat messages appearing in wrong order Bug chat	16	346	January 26, 2025
Chat messages being processed out of order Bug chat	2	70	November 18, 2025
Moving chat messages to a new channel jumbled them all up Bug chat	15	944	June 12, 2022
Chat: inconsistent time format for consecutive messages from the same user UX chat	2	53	June 12, 2025
Replies on channel dropping to top Support chat	4	226	May 28, 2024

I'm having issues sending DMs or channel messages in rapid succession

Related topics