A user, NateDhaliwal, reports that their topic list shows ‘Latest (1)’ and ‘New (1)’ despite having no unread or new topics, even after reloading and logging out. Moin asks if the issue persists after reload, which NateDhaliwal confirms. nobrowser explains this is a common issue across Discourse sites, likely due to delayed synchronization between load-balanced servers, making it feel like a bug but technically expected behavior. NateDhaliwal asks if it resolves over time, and nobrowser says it eventually does, which adds to the frustration. NateDhaliwal notes it’s not fixed by logout/login. Later, NateDhaliwal identifies the issue as stemming from the Documentation category and NateDhaliwal concludes it’s resolved after reading a specific topic, which appeared as unread in /new.
Here on Meta, my topic list says Latest (1) and New (1), but I don’t have any new topics on my list. Going to /new says that there are no new topics.
Do the numbers stay after a reload of the site?
Yes, it does. It also doesn’t reset after I read an actual unread topic.
Something like this happens to me all the time, on multiple discourse sites (not just Meta). It’s a bit like the experience with Gmail, where you can delete a message (or take some other action) and it’s not reflected in the UI until you reload, sometimes reload multiple times. I ascribe it to hitting a different load-balanced server every time from a pool which synchronizes only “lazily”. Yes, super annoying but it seems it’s how we should expect sites to “work” now 
–
Ian
Does it go away after a while or will it remain forever?
For me, it always resolves eventually. In a way that makes it even more annoying because I can see how it can be argued it’s not a bug.
I see. It’s infuriating, because even a log out and log in doesn’t solve the issue.
Well, it seems like the topic comes from Documentation . That’s a big help.
Seems fixed now after I read the Plugin tutorial Part 1 topic. It appeared in my /new, as unread.
Oh well, it’s fixed now.
