# Chat notifications not showing for replies in chat channels

**URL:** https://meta.discourse.org/t/chat-notifications-not-showing-for-replies-in-chat-channels/410620
**Category:** Bug
**Tags:** notifications, chat
**Created:** [21 באוגוסט,‏ 2026,‏ 2:16pm UTC](https://meta.discourse.org/t/chat-notifications-not-showing-for-replies-in-chat-channels/410620 "2026-08-21T14:16:35Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Moin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/moin/32/554653_2.png) [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [21 באוגוסט,‏ 2026,‏ 2:16pm UTC](https://meta.discourse.org/t/chat-notifications-not-showing-for-replies-in-chat-channels/410620/1 "2026-08-21T14:16:35Z")

</div>

Continuing the discussion from [Issue with Chat Icon Badge Count Not Showing for Direct Messages (DMs)](https://meta.discourse.org/t/issue-with-chat-icon-badge-count-not-showing-for-direct-messages-dms/384734/5):

I think there is the same problem with chat channels. Users do not see the notification dot when you reply to their posts and threading is disabled.

Screenshot from my repro:

 ![image](https://global.discourse-cdn.com/meta/original/4X/f/a/1/fa18de5ff6008d5645ad7b351d0dc5a740c05acf.png)

Steps to reproduce:

1. Create a new chat channel, **don’t** enable threading
2. Write a message (I wrote 2 for my screenshot above because the reply indicator is hidden on direct replies, but it also works with one)
3. Impersonate a test user
4. Join the channel
5. Reply to the message the admin wrote; there should be the indicator that you are replying to another message  
 ![image](https://global.discourse-cdn.com/meta/original/4X/e/4/6/e46b37acd79ea50ababd0019ccf0b1d387070f24.png)
6. Stop impersonating
7. Check your notifications

**Expected result** : There is a dot next to the channel in the sidebar, on the header icon and on channels in the menu where you switch between DMs and channels.  
**Actual result** : Without looking at the channel there is no indicator that there is an unread chat message, which is even more problematic because someone was directly replying to you. You are notified better about someone posting something than about someone replying to you

---

<div class="post-metadata">

### Author: ![awesomerobot](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/awesomerobot/32/142900_2.png) [@awesomerobot](https://meta.discourse.org/u/awesomerobot)
#### Post date: [9 בספטמבר,‏ 2026,‏ 2:29pm UTC](https://meta.discourse.org/t/chat-notifications-not-showing-for-replies-in-chat-channels/410620/2 "2026-09-09T14:29:53Z")

</div>

Thanks for reporting it! one additional note is that this is a client/server mismatch… if I keep the same window open and open a test user in a different browser, the notification dot can appear, but it goes away on refresh despite not changing the read state. Impersonation effectively causes the same behavior as the refresh.

This will fix it

> <https://github.com/discourse/discourse/pull/43479>
>
> Replying to someone in a channel with threading disabled leaves no unread indica…tor, because the reply was tracked as a thread message while rendering in the channel stream. Essentially we have an expectation that the threading interface will handle this state, but don't have coverage when threading is disabled. 
> 
> This fix counts those replies against the channel's read marker, so both the unread dot and mentions inside the reply now show up when threading is disabled. 
> 
> Issue originally reported here: https://meta.discourse.org/t/chat-notifications-not-showing-for-replies-in-chat-channels/410620
> 
> To repro: 
> 
> 1. Create channel with threading disabled
> 2. Post a message in that channel, then navigate away from the channel
> 3. Open an incognito window and log in as a different user
> 4. Join the channel and reply to that first message 
> 5. Switch to the original user, and note that you can see the unread dot in the sidebar
> 6. Refresh the page, you'll notice the unread dot in the sidebar goes away despite not having visited the channel
