# Notification number not updated on new message
**URL:** https://meta.discourse.org/t/notification-number-not-updated-on-new-message/37538
**Category:** Support
**Created:** [January 6, 2016, 3:50pm UTC](https://meta.discourse.org/t/notification-number-not-updated-on-new-message/37538 "2016-01-06T15:50:45Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@MK2k](https://meta.discourse.org/u/MK2k)
#### Post date: [January 6, 2016, 3:50pm UTC](https://meta.discourse.org/t/notification-number-not-updated-on-new-message/37538/1 "2016-01-06T15:50:45Z")
Hi,
The notification number (as seen in the little screenshot below) doesn’t get updated when a new unread message has been sent. This wasn’t always the case so I assume it’s a bug and not by design. It seems to act this way since the balloon icon has been removed and messages have been merged into the avatar icon in one of the recent updates.
affected version: v1.5.0.beta6 +104
screenshot:
cheers
– MK2k
---
### Author:  [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [January 6, 2016, 8:24pm UTC](https://meta.discourse.org/t/notification-number-not-updated-on-new-message/37538/2 "2016-01-06T20:24:10Z")
What browser are you using? Can you reproduce on [http://try.discourse.org](http://try.discourse.org) (you can create multiple accounts)?
---
### Author:  [@MK2k](https://meta.discourse.org/u/MK2k)
#### Post date: [January 6, 2016, 8:49pm UTC](https://meta.discourse.org/t/notification-number-not-updated-on-new-message/37538/3 "2016-01-06T20:49:58Z")
Browser is Firefox 43.0.1.
I can’t reproduce on [try.discourse.org](http://try.discourse.org), there a number with green background is shown when a message arrives. Therefore I assume the browser isn’t to be blamed.
More observations (in my discourse instance):
1. even the list which opens up when the avatar is clicked does not update with either a new message (within an already created thread) or a completely new created message thread
2. A “like” of a post within a message thread generates a notification (the blue one though)
---
### Author:  [@MK2k](https://meta.discourse.org/u/MK2k)
#### Post date: [January 11, 2016, 9:45am UTC](https://meta.discourse.org/t/notification-number-not-updated-on-new-message/37538/4 "2016-01-11T09:45:49Z")
Not a bug then? Oh well…
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [January 11, 2016, 10:44am UTC](https://meta.discourse.org/t/notification-number-not-updated-on-new-message/37538/5 "2016-01-11T10:44:42Z")
Needs consistent repro steps to be a bug…
---
### Author:  [@MK2k](https://meta.discourse.org/u/MK2k)
#### Post date: [January 11, 2016, 11:07am UTC](https://meta.discourse.org/t/notification-number-not-updated-on-new-message/37538/6 "2016-01-11T11:07:35Z")
Maybe it’s not that easily identifyable and/or depends on more than just a few repro steps in the try-discourse area.
If there are any scripts / debug modules available that help narrow the issue down, please let me know. I’d be very happy to keep the analysis going. I fear however, that re-labeling a potential bug as support will add the issue to a sea of unresolved support issues 😑
---
### Author:  [@MK2k](https://meta.discourse.org/u/MK2k)
#### Post date: [January 19, 2016, 4:27pm UTC](https://meta.discourse.org/t/notification-number-not-updated-on-new-message/37538/7 "2016-01-19T16:27:25Z")
Updated to v1.5.0.beta8 +102, the green notifications are back. It could have been an issue with sidekiq (not too sure about that however).
This case can be closed now.
---
### Author:  [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [January 19, 2016, 4:38pm UTC](https://meta.discourse.org/t/notification-number-not-updated-on-new-message/37538/8 "2016-01-19T16:38:34Z")