Permanent Unread but empty post in Cubase category

csurieux · June 2, 2026, 6:33am

Everyday I open the forum, Cubase category, I see an Unread (1) (Topics you are currently watching, or tracking with unread posts).
But when I click it there is no post, this filter brings nothing.
How to fix this ?
It seems I have lost access to one of the topics I participated in in the past ?
This is not a cookie as I also get this on my mobile and desktops and I have deleted cache datas ???
Am I the only one ?

wolfger · June 2, 2026, 8:03am

Confirmed!

SF_Green · June 2, 2026, 8:11am

Same here. Have you muted any posts that you formerly were subscribed to? That’s what I suspected in my case.

gerardka · June 2, 2026, 10:48am

same here

Nico5 · June 3, 2026, 12:52am

Same here.

Reco29 · June 3, 2026, 6:30am

This seems to be a well known issue which can be caused by a number of different reasons. Been there myself…

Although this forum is run by Steinberg, it is based on the Discourse platform. There are a number of approaches to get rid of remaining ghost answers. Try to describe your exact problem in a search query and include the words “Discourse forum”. I got it sorted out in no time after it had been driving me crazy for weeks…

HTH

csurieux · June 3, 2026, 7:09am

It looks like a platform bug :

github.com/discourse/discourse

FIX: Unread count could disagree with the /unread topic list (#40473)

committed 02:07PM - 02 Jun 26 UTC

ZogStriP

+25 -1

The "Unread (N)" badge could count a topic that did not appear on the /unread pa…ge (and, conversely, a genuinely unread topic could be hidden from /unread). See https://meta.discourse.org/t/-/403986. Both the count and the list bound their results by the user's "old unread" cutoff, `user_stats.first_unread_at`, which is computed from `topics.updated_at`. The count (TopicTrackingState) filters on `topics.updated_at >= first_unread_at`, but since 17555ae8798 (#40127) the /unread list (TopicQuery#apply_max_age_limit) filtered on `topics.bumped_at` instead. A small action at the tail of a topic (close, auto-close, category change, ...) moves `updated_at` but not `bumped_at`, so such a topic passed the count's filter yet failed the list's filter: it was counted but never listed. #40127 switched to `bumped_at` for suggested topics, where bounding by last visible activity is the desired behaviour, so reverting it is not an option. Instead, `apply_max_age_limit` now takes an explicit `age_column` that defaults to `updated_at` (keeping the unread and new lists consistent with the count), and the suggested-topics callers pass `age_column: :bumped_at` to preserve their behaviour.