Stuck notification

[TriMoon]

Select Topic Area

Bug

Body

I have a notification i can't get rid of, even after multiple reloads etc...
The notification in question is not even shown, but it is listed in the listings as can be seen in the screenshot.
How can i get rid of this one?

Similar to #32380,#32712

[linuxlawson]

There are some suggestions here that should help you: #6874

Like this:

Goto Done.
Select all
Move to inbox
Goto Inbox
Select all
Mark as read
Mark as Done

[stringang]

The suggested method is useful, my problem is solved.

[ryanmkurtz]

This worked for me too. I had to select more than the current screen showed but after I selected enough of my history and performed the steps, it worked.

[oncet]

First time it didn't seem to work. Tried once more buy this time moving a lot more of done notifications to the inbox and it worked!

[LiberiFatali]

This works. Be aware that if you have multi-pages, after selecting the first page it will show a link to select the rest.

[vgdh]

That method magically works.

[queenofcorgis]

Thanks for posting in the GitHub Community, @TriMoon !

We're happy you're here. You are more likely to get a useful response if you are posting your question in the applicable category, the Issues category is solely related to conversations around the GitHub products Issues and Projects. I've gone ahead and moved it for you. Good luck!

[TriMoon]

Thanks, but thats all i could do using the presented UI while creting this topic...
We're not able to manually select categories...

[queenofcorgis]

Hi there - glad to see your notification is no longer stuck, but would you mind elaborating on what you mean by you're not manually able to select categories? We want to make sure you have the best experience in Discussions.

[TriMoon]

Well TBH, i forgot the exact steps i took to post this issue because it was my first time on this board.
But if i would have been able to select categories im sure i would have done so, because im used to use categories all over the web 😉
Anyhow the bug has dissolved itself as i mentioned in my marked post 🖖

[queenofcorgis]

Thanks for the quick response - if you encounter anything like that with the categories again - please give me a ping!

[TriMoon]

Somehow they seem to have fixed my issue Behind the scenes because it's gone without me doing anything except posting this thread 🤣

[ryanmkurtz]

I too have a stuck notification now.

[Nuc1eoN]

https://github.com/orgs/community/discussions/43032#discussioncomment-9456373

[oncet]

I'm having the same problem I think.

It seems to be coming from this particular repository but I tried all kind of filters and nothing shows up:

It's getting pretty annoying, anyway I can get rid of it?

[fernandoxu]

same! even if I set stop ignoring

[fvlasie]

I am experiencing the same issue. I tired all the steps mentioned here but I cannot resolve it. I have 3 repos with notifications that do not show when I click on them so i cannot mark them as done.

[Nuc1eoN]

try https://github.com/orgs/community/discussions/43032#discussioncomment-9456373

[M-Reimer]

I also have a "stuck notification". Still someone watching here who can fix this for me? I tried everything...

[Nuc1eoN]

Same here. No notifications left but still getting the blue dot.

[M-Reimer]

Yeah but noone seems to care. Still have the problem.

[Nuc1eoN]

This fixed it for me: https://github.com/orgs/community/discussions/43032#discussioncomment-9456373

[andrewjswan]

I also have a "stuck notification". Still someone watching here who can fix this for me? I tried everything...

[Nuc1eoN]

This fixed it for me: https://github.com/orgs/community/discussions/43032#discussioncomment-9456373

[M507]

Same issue here..

[Nuc1eoN]

This fixed it for me: https://github.com/orgs/community/discussions/43032#discussioncomment-9456373

[Nuc1eoN]

This has resolved it for me.

You have to create a GitHub token, select "Access notifications" and create it.

Copy the token and in your console run export TOKEN=<your-token>.

Then copy and paste this into your console and run it:

curl -X PUT \
   -H "Accept: application/vnd.github.v3+json" \
   -H "Authorization: token $TOKEN" \
    https://api.github.com/notifications \
   -d @<(cat <<EOF
   {
     "last_read_at": "$(date -u +'%Y-%m-%dT%H:%M:%SZ')"
   }
EOF
)

[SonoSooS]

(see this for full explaination)

You can go to https://github.com/notifications, and run this script in Inspect Element console:

(function(doc,endpoint)
{
    const a=doc.querySelector('form[action="'+endpoint+'"]');
    const b=doc.createElement("input");
    b.type='hidden';
    b.name='query';
    b.value="";
    a.appendChild(b);
    const c=doc.createElement("input");
    c.type='hidden';
    c.name='mark_all';
    c.value="1";
    a.appendChild(c);
    a.submit();
})(document,"/notifications/beta/mark");

If it doesn't make the ghost notification read, replace mark with unmark in the last line of the script, run that first, and then run mark again, and that should make the ghost notification read.
Sadly this doesn't get rid of the ghost notification (so notification pagination will be still broken), but at least the unread bubble can finally go extinguish :)
This method also works if you can't dig up more notifications to make it at least 26 to use the scriptless method.

[roniemartinez]

Worked for me but now the repo is still stuck on the Repo list.

[SonoSooS]

It should time out after ~30d, I think.

Since we have no way to query all notifications, and thus we can't flag it as done, you'll have to live with it until it either magically pops back up, or until it times out by itself.

[arose26]

Worked for me when all else failed (the cause was a notif in a repo that was deleted). Thanks!

[qndel]

Got a stuck notification because dude opened a discussion in my repo, was getting notifications from it, then dude somehow got DELETED along with his discussion yet notification is permastuck, this is so annoying