# Latest (1) and New (1) even though there are no more unread and new topics

**URL:** <https://meta.discourse.org/t/latest-1-and-new-1-even-though-there-are-no-more-unread-and-new-topics/337653>\
**Category:** Product Support\
**Created:** [November 22, 2024, 2:36am UTC](https://meta.discourse.org/t/latest-1-and-new-1-even-though-there-are-no-more-unread-and-new-topics/337653 "2024-11-22T02:36:53Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![nobrowser](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/nobrowser/32/240031_2.png) [@nobrowser](https://meta.discourse.org/u/nobrowser)\
**Post date:** [November 22, 2024, 7:52am UTC](https://meta.discourse.org/t/latest-1-and-new-1-even-though-there-are-no-more-unread-and-new-topics/337653/4 "2024-11-22T07:52:42Z")

</div>

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

---

_[View the full topic](https://meta.discourse.org/t/latest-1-and-new-1-even-though-there-are-no-more-unread-and-new-topics/337653)._