In my user account, the Inbox Unread indicator (the dot in the Inbox menu and in the browser tab title) is not clearing no matter what I do.
I have cleared cookies, cleared browser site data, rebooted, re-logged in, set my inbox view to “All”.
This is the third time this has happened in the past few months, and I haven’t gotten good answers from support.
It eventually clears itself (many hours later or next day) but it’s frustrating as I take action on whether or not I have any unread messages. It means I need to keep Asana up in a live window versus letting it sit minimized.
I’ve seen other similar topics, just hoping to get some more attention on this.
Thank you in advance for any suggestions on resolving this.
I just want to report seeing exactly the same thing @Todd_Binder describes. It’s also occurred for me more than once over the past few months, including yesterday or the day before, lasts a little while, then corrects. I think there’s an intermittent bug.
There are no filters in place on my inbox and it is happening again today. This is at least the fourth time this has happened to my account over the last year.
It’s also happening to me and it’s a problem, because my team communicates additional tasks under tasks that already exist, so I rely on that indicator to let me know if I need to do something.
Yup - same here. Just started happening today. Spent the last 20min going through every single one of my messages to ensure I’ve scrolled the thread to trigger any code that would clear the red dot. No dice.
Update here. I just noticed that the red dot cleared as soon as another user replied to or posted on a recent thread. Not sure if this helps shed light at all, just a behavior I noticed as it occurred. But red dot is gone for now.
This bug seems to recur every so-many months. I’m seeing it again currently in the last few days, intermittently, after not experiencing it for months.
@Forum-team, this is a sustained, though intermittent, problem, seen by multiple folks, so perhaps it’s worth escalating while it’s happening in case developers might be able to quash it once and for all.
Thank you for bringing this up; we’ll review it and share it with the team.
To set expectations, while I understand it can be frustrating, this issue is more of a visual inconvenience rather than a blocker. As the team is focused on higher-priority tasks, it may take a little time to address.