Whenever I open Meta now, it goes to topics 1-2 days old, begore showing a ‘xx new or unread topics’, usually around 30, and when clicking on that, shows the actual recent topics.
Furthermore, (I believe this is related) there will sometimes be a count of New replies which I can’t seem to get rid of, but will disappear later.
I tried clearing my cookies and logging back in, but although it fixed it for a day, I’m experiencing it again.
And it’s not just 1 day. Earlier today, it was 2 day-old topics. Just now, I had 3 day-old topics with ‘62 new or updated topics’.
Is there a fix on my part?
Is anyone else experiencing this issue?
is the same bug as Information about topic is not updated when using new & unread topics banner?
I’m not sure if Nate’s experience is the same, but to me, it feels more like jumping back to where I was hours ago when the tab has been inactive for a while. So I use the forum, get back to it later, and don’t start where I finished before, but where I started. So the unread count includes all topics I read a few hours ago.
Yesterday, it even looked like I was logged out again until I refreshed the page.
But it seems way more than that. It’s not just a few hours, but multiple days. Which is quite odd since I have been on Meta after that period on my phone.
Maybe it’s when you last logged in or something like that? I log out quite often
Hmm… I rarely log out though. Still, an interesting hypothesis. After all, I did log out just a few days ago to try and reset this. I will see if it becomes 4d topics tomorrow, if so, log out and see the next day if it goes back to 1d.
So it’s odd behaviour. I didn’t logout, but today shows 1d old topics. This seems quite erratic, and I’m trying to think what I might have done recently that could have caused this (and recent PRs don’t show any hint).
Just yesterday I hit 5d old topics when I opened Meta. I think I’ve figured out a repro and reason.
I think this happens when you scroll down in the (latest?) topic list past say, the first load more section.
I managed to repro this on another device as well.
Can anyone else repro this? Or is it just me? I haven’t heard anything for months…
Just yesterday and today, I’m getting topics from a few days before, and it shows ‘See 22 new or updated topics’, which then shows new topics upon clicking that.
Happens on Chrome (Android) and Safari.
I see all kinds of problems where I am seeing stuff from some time ago. It even results in an interface that shows a login button at the top while I already logged in this morning. A reload helps to fix that, but sometimes this is really confusing.
We are either experiencing the same issues (but yours sounds more extreme: I don’t have the login button issues), or it’s entirely different. I check Meta daily, so it’s not like these topics are unseen: they have all been read already. I’ll try and attach a screenshot the next time I’ve seen it.
In the meantime, I’m trying the repro steps above to see if it helps “refresh” to current topics.
It might be a bit unusual but I log out every day, I don’t expect you to do that which explains why that doesn’t happen for you.
Okay, I’ve got 2 screenshots that should help.
1: Opening the tab, seeing 1d old topics.
2: Clicking on ‘See 21 new or updated topics’ (now the correct view).
A side effect of this bug is that I would get a random (3) supposedly new topics (or any number), but disappears when I choose New in the topic list.
UPDATE: Curiously enough, after leaving the tab and coming back immediately after, although I was right at the top of the topic list, it suddenly jumped to around the topics in the 1st screenshot.
Here is a screen recording of the issue (ignore the bar at the top and the lines on the screen).
Thankfully, a reload gixes this last problem, but not the original one.
I have only a screenshot. It’s one showing the opposite of what I described above. This time it suddenly seemed as if I was logged in while I was not. This is way more spooky.
app.js:367 ℹ️ Discourse v2026.7.0-latest — https://github.com/discourse/discourse/commits/8b552f97d2 — Ember v6.10.1
chat/api/me/channels:1 Failed to load resource: the server responded with a status of 403 ()
u/Moin/private-message-topic-tracking-state:1 Failed to load resource: the server responded with a status of 403 ()
ajax-error.js:15 TypeError: Cannot read properties of undefined (reading 'forEach')
at pm-topic-tracking-state.js:257:34
Wc @ ajax-error.js:15
chat.js:231 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'meta')
at Ff.setupWithPreloadedChannels (chat.js:231:22)
at chat.js:212:18
I know you might think logged out in another tab. But I did not. This device was not logged in on Meta today before I logged in to write this report (earlier posts today were written on a different device). Also when I have two tabs and log out in the other one I usually see
So this is unexpected, and it makes me wonder whether something similar could happen on a shared or public computer. I’m not worried about someone gaining access to my account - but even showing the previous user’s avatar could be a privacy issue. On Meta that’s not particularly sensitive, but on forums discussing health, politics, or other personal topics, someone might reasonably not want the next person using the computer to be able to associate them with their account.
It just happened a second time:
This time I tried to visit my PMs and instead of “this page is private” I got a simple oops page
At this point, I think these are separate bugs that we are experiencing. I don’t experience the problems you described, and not sure if anyone experiences mine.
Also: could this be the longest bug report topic with no staff intervention??
I experience your problem. I am just sharing the extreme cases, because I hope those make this bug topic a little more important. I understand that I am probably the only one who logs out every day (or even multiple times during the day), which is why I might be the only one where the problem has these effects. But I still think the problem is the same. In both of my screenshots you can see that the topics at the top of /latest were not updated in the past minutes and that the new topic banner shows multiple new topics available. But I was reading on Meta. Using the back button should not have caused me to see /latest as it looked like yesterday or a few hours ago. (And in my case it shouldn’t pretend I was logged in/out when I am currently not.)
Got it. Aplogies for the oversight. But I’m surprised there has been no staff intervention yet 
.
