Timeline fails to load after clicking the ^ to go to the first unread message

[kittykat]

Steps to reproduce

This only happens sometimes, I can't see a pattern for triggering it

1. Click the ^ to go to the first unread message

Outcome

What did you expect?

Older messages load

What happened instead?

Got a blank view in the timeline with this error message, this has happened twice today:

Operating system

No response

Browser information

Chromium 96.0.4664.45 (Official Build) Arch Linux (64-bit)

URL for webapp

develop.element.io

Application version

Element version: 211f480-react-f4a94f6e7f18-js-f30be8787934 Olm version: 3.2.8

Homeserver

No response

Will you send logs?

Yes

[kittykat]

I've just hit the issue again and got this in the console (and attaching another rageshake):

[t3chguy]

That is the server claiming it doesn't know that event, not much the client can do here

[MadLittleMods]

Related to #20927

Same symptoms but it is a different error unless the logs changed over the month.

[rettichschnidi]

Seeing this all the time on my own home server. Likely connected: We have a retention policy of max. 90 days.

Example:

1. Chose a room with "unread messages"
2. Click on the "Jump to first unseen messages" button
3. This exact error display gets displayed

I experience this on my own Synapse home server and I am willing to investigate - please let me know how I can help.

[t3chguy]

@rettichschnidi I'd say Synapse should probably move the RM marker when applying a retention policy otherwise all clients would experience this. There's no way for a client to know if a given event ID falls outside of the current retention window as enforced by your server.