Edit history

A user received a system DM while the Web client was not running. The same system DM was immediately visible on mobile. When the user later opened the self-hosted instance in the Web browser, the system DM did not appear at all. There was no system DM conversation visible in the DM list. I then sent a second system DM directly to the same user while the Web client was open. At that moment, the system DM conversation appeared in the Web client — and both the new message and the previously missing message were visible. This indicates that the first message had already been stored and was available in the conversation history, but the existing system DM conversation was apparently not loaded or shown when the Web client started.

1. Make sure the recipient is not currently using the Web client / close the browser.
2. Send a system DM to the recipient.
3. Confirm that the system DM is received on mobile.
4. Open the self-hosted instance in the Web browser.
5. Observe that the system DM conversation is not shown in the DM list.
6. While the Web client is open, send another system DM to the same recipient.
7. The system DM conversation now appears.
8. Both the newly sent message and the older message that was previously missing are now visible.

Expected behaviour: Existing system DM conversations and their messages should be loaded and displayed when the Web client starts, regardless of whether the client was online when the message was originally sent. Actual behaviour: The system DM conversation remains hidden until another system DM is received while the Web client is active.

Stable Web 2026.1003.2520, Linux (x64), Firefox 157.0, Locale en-US

The screenshot was taken after the second system DM was sent. Both messages are visible, including the first message that had previously not appeared in the Web client. image