GUIDES · BETSLIP DOCTOR
Does Mark all read also clear club notifications that arrive later?
No. A successful Mark all read advances the server’s read-through point to the current inbox sequence when the command is processed. Activity arriving after that point is new to the read boundary and may still be unread.
For BSD readers handling this notification task · Updated
The command covers a current sequence
Mark all read does not mark every future notification as read. BSD stores a read-through sequence for the account. When the read-all command is processed, the service sets that boundary to the sequence current at processing time.
That boundary is not necessarily the exact instant you tapped the button. It is the successful server operation’s sequence, which is why a notice arriving afterward can remain unread.
A later reply or like sits beyond the old boundary
If a free-club reply or like enters the inbox after the read-through point, it has a later sequence. The prior read-all action does not reach forward and clear it. Check the row’s unread state in the current inbox.
If you retry an uncertain saved read action, BSD reuses that same command and its original result. A retry is not a new read-all request and does not extend the old boundary to activity that arrived later.
Handle new activity on its own
If later activity appears and you want it read, use the current row or start a new read action after it appears. This guidance applies to recorded free-club reply and like rows only; it does not promise that every interaction creates a notification.
A reply arrives after read-all
Suppose a member marks the current inbox read and a new free-club reply is processed afterward. That reply is beyond the boundary recorded for the earlier action, so it can appear as new unread activity rather than being cleared retroactively.
Related questions
Does a retry clear new items too?
No. The saved retry repeats the original read command and uses its original result; it is not a new mark-all action.
When is the read-through boundary set?
The backend sets it to the current sequence when the read-all command is processed, not necessarily at the exact moment the member tapped.