Deleting the last post in a topic confuses read tracking

In my self-hosted install, I have a topic where the last post has been deleted. This topic shows up as if it still had unread posts:

Reading the post again doesn’t help. I do have an entry for this post in post_timings.

One of my users is also experiencing the same issue in another self-hosted install.

I don’t have consistent repro steps. When I confirmed the report from one of my users, the topic appeared grayed out for me; and later on, it returned to black, although no changes were made to the topic.


I see this quite frequently on our instance. I couldn’t say whether or not it happens in every instance where the last post has been deleted. I’ll try to remember to watch more closely and take note.

1 Like

Thanks but it’s a known issue and the fix unfortunately requires a large refactor. It will happen but not in the near future.