Unclearable Badge Notifications in Monday CRM

Hi, everyone.

I’m in Monday CRM, and I just assigned three tasks to a co-worker. There is nothing in my automations that would trigger a notification back to me, I did not tag myself, and I would never program that sort of thing anyway. (I don’t need to tell myself about a task that I created and gave to someone else!)

That annoyance aside, I went ahead and opened each of the three … but the badges won’t go away. I even clicked on Read More for each task, just to drive home the point to CRM that I had truly “opened” the task. It didn’t matter.

I also went to my bell notifications area to click Mark All as Read. Nothing. I also checked both browsers (Edge and Firefox), clearing the cache for each, closed and reopened the desktop app, and rebooted twice - including one “cold” shutdown with a 10-second count-off. Nothing.

To make an elite political statement, I even logged on with the co-worker’s username and password to check their screen and open each notification for the same three tasks as if I were them. (As task recipient, and as the solitary target of my automation, this is the only person who should have received badge notifications in the first place.) Their situation is even weirder. Their board still clings to two of the three badges … but one has abruptly cleared. I have no idea why, so I can’t even replicate the solution.

In sum, the task “recipient” read all three messages and could clear only one badge. The task creator (me) was never designated to received notices at all, got all three badges anyway, and none of them will go away.

image

Any ideas?

Tom

Ps. If it will help debug, I noticed that I also now have a new badge slapped onto a fourth task … one that I self-assigned two days ago and have long since reviewed - at least twice.

Wow, that sounds incredibly frustrating! I’ve run into similar quirks in Monday CRM where badges just refuse to clear, and it often ends up being some weird sync or caching issue between the app and browser. One thing that’s helped me is documenting each automation and notification setup carefully so you can spot conflicts or redundant triggers tools like Phonexa have been surprisingly useful for keeping track of these workflows in other projects, and I could see it helping here to map out which notifications are firing and why.

Sometimes just having that clear overview makes it easier to troubleshoot these “phantom” badges without having to experiment blindly.

Hi Tom,

Just so I am understanding this properly, this is on the item update right?

Update: It’s a known bug that they’re working on resolving. The counter should start resetting again soon and behaving like normal.