Looks like a server-side change in Discord is causing Ripcord to not recognize the response when trying to sync unread markers. When that happens, as a precaution, Ripcord gives up any further attempts to sync read markers for that session. I'll look into this and see what I need to change.

Any updates or help you need from us? I've at least one server where the behavior is consistent every time I open Ripcord on my laptop.