Opening a community with an unread channel sometimes leaves the new message missing until refresh

(#3893) Bug Open: Needs triage channels community messaging

Can you reproduce this?

This bug has a 50 XP repro bounty. Follow the steps in the report on your own device and tell us what happened.

Sign in to post a reproduction.

Reproduction steps

(best guess, not confirmed)
  1. Open Fluxer on web or desktop.
  2. Don't open community A at all during this session.
  3. Wait until community A shows an unread in the community list.
  4. Click community A. It opens to the channel that has the unread.

Expected behaviour

The channel shows the new message and the unread clears.

Actual behaviour

The unread stays stuck and the new message isn't shown. Refreshing the client shows the message and clears the unread.

Build information

Canary Desktop 2026.1009.45608, Web 2026.1011.165018, macOS 27.0.1 (arm64), Electron 44.4.1, Chrome 152.0.7977.78, Node 24.21.0, Locale en-GB

Platform

macOS, Windows, Linux, Web

4 comments

Sign in with Fluxer to comment and vote.
Comment by marcy
marcy 1 vote Could not reproduce on Linux 1 reply
Could not reproduce Platform: Linux Build information: Canary Desktop 2026.1009.45608, Web 2026.1011.165018, Linux 7.2.7-arch1-1 (x64), Electron 44.4.1, Chrome 152.0.7977.78, Node 24.21.0, Locale en-US tried reproducing with multiple new sessions but couldn't reproduce it
Comment by Dinosaur Gnatalie
Dinosaur Gnatalie 1 vote Could not reproduce on Linux
Could not reproduce Platform: Linux Build information: Canary Desktop 2026.1009.45608, Web 2026.1011.165018, Linux 7.2.9-200.nobara.fc44.x86_64 (x64), Electron 44.4.1, Chrome 152.0.7977.78, Node 24.21.0, Locale en-US White unread dots disappear and new messages are shown. The red "NEW" line doesn't clear until I move away from the channel.
Comment by probablyjassin
probablyjassin 1 vote Could not reproduce on Linux
Could not reproduce Platform: Linux Build information: Canary Desktop 2026.1009.45608, Web 2026.1011.165018, Linux 7.2.9-2-cachyos (x64), Electron 44.4.1, Chrome 152.0.7977.78, Node 24.21.0, Locale en-US Tried ~8 times, a couple different scenarios like when the unread message in the community is in a different channel from the one you land in when clicking the community. Each attempt, I restarted Fluxer in a different community to best emulate "open fluxer and don't open the community at all". Couldn't reproduce, didn't notice any other irregularities either