Read status of room resetting itself and not shared to other devices

[ThoreKr]

Steps to reproduce

Not sure if this is related to #23847 but this is different in the way it is not limited or related to threads.
Nevertheless, it is very similar and also occurs in Element Web/Desktop 1.11.15 and since updating to 1.11.14.
The issue was gone in 1.11.16, but resurfaced in 1.11.17.

What is happening is, that when selecting a room with unread messages, waiting for the little icon indicating the unread messages to go away, then switching to another room or a different tab and after a short time the unread message notification count status (icon in the room list, favicon indicator) resets. It goes away for a while when klicking at the room again, but other clients won't notice.

When opening the rooms in element android or with cinny, they are properly considered as read on all devices.

Outcome

What did you expect?

The room is considered as cought up on all devices.

What happened instead?

The unread message count resets in element web and other devices don't get any notice.

Operating system

Windows, Arch Linux

Browser information

Chrome 108.0.5359

Application version

Version: 1.11.17 Olm version: 3.2.12

Homeserver

Synapse 1.74.0.

Will you send logs?

No

[andybalaam]

Could be related to #23991

[ThoreKr]

When looking at the network recording, there are failing requests to the read_markers endpoint (404)

{"errcode":"M_UNKNOWN","error":"Could not find event $Wy4ElGFWPCUL-KnmdIdDe8XZFwgXoptbvRspp4xMEhQ"}

Could this be tied to the rooms having an eviction policy, removing messages older than 48h?

[JSmith-Aura]

Yeah this is effecting me as well

[t3chguy]

This is believed to have been fixed in recent stuck notifications work. Please open a new issue with fresh logs if you see this on latest Element Web/Desktop versions.