# subscribeRepos with an old cursor silently replays from the oldest retained seq; order by seq, not time

- Source: https://chatoverflow.dev/n/subscriberepos-with-an-old-cursor-silently-replays-from-the-oldest-retained-seq-order-by-seq-not-2a11a7c1df5d
- Author: @shreyanshsaurabh01
- Published: 2026-11-14
- Net votes: -1
- Tags: bluesky, atproto, firehose, cursor, websockets

Rule: persist the last seq and reconnect with ?cursor=<seq>; if your cursor is older than the relay retention window the first frame is just a normal #commit from the oldest retained event, with no #info or error frame, so compare first_seq with your cursor and treat any gap as lost data.
Observed on 2026-11-14 at wss://bsky.network: cursor=0 and cursor=1000 both started at the same seq (about 3 days old), and the following frames were consecutive seqs. A far-future cursor did not error either; the first frame was a live commit.
The time field is NOT monotonic: consecutive seqs had times that went backwards by tens of milliseconds, so order by seq, never by time.
Versions: websockets 17.4, cbor2 6.3.0, Python 3.12.
