Github says I have notifications but will not show them

[adisib]

Select Topic Area

Bug

Body

Github is telling me that I have 3 notifications, but it will not show them or let me mark them as read. This prevents me from being able to tell if I actually have notifications via the icon on the top-right of each page.

[bewuethr]

I have the same issue; I can only see some notifications when I select the repository they're related to on the left-hand side. I'm member of an organization with single sign-on, and when not logged in to that organization, I don't expect to see those notifications, but there are notifications outside of that org that I can't see.

For example, unfiltered inbox showing no notifications:

Selecting the dependabot/dependabot-core repository shows the missing notification:

[ioSpark]

I'm having the same issue, and it appears to be SSO related. When I'm not signed into an org, then the notifications will be inaccurate, sometimes showing 4 per page, or none per page, and the counts for inbox being inaccurate. Signing in seems to fix that. Though I would expect either for the notifications not to show, or to tell me something like "X notifications from Y org, sign-in to see".

Also worth noting that none of the filtering options work correctly in that case. If I try to filter per-repo, then it will often only show a few items, with lots and lots of pages.

[Abdeali099]

I have same issue. Can you help me to resolve that?

[lwise]

I have the same issue, but my ghost notification is for an org/repo that I do not belong to (it shows 404 when I search for it).
When I click that repository in the notifications sidebar, the missing notification is not shown. I am unable to clear my notification indicator.

[KindaBrazy]

Same here!

[Caranell]

same here

[edgar-bonet]

Same here, and I do not use single sign-on.

Just like @lwise, my ghost notification is from a non-existent user and repo (both return 404). For me it's ycombinatorrr/ycombinator-notification:

[zhangysh1995]

Same problem and same repo here

[tigerjack]

I have the same issue with these two repos. Note that the name is not exactly the same as your ycombinatorrr, which I don't know exactly how to interpret.

[felladrin]

This is a similar discussion from https://github.com/orgs/community/discussions/174310, where the solution was to use a command line to delete those invisible unread messages.

[Abdeali099]

This is a similar discussion from https://github.com/orgs/community/discussions/174310, where the solution was to use a command line to delete those invisible unread messages.

Hi, Thank you so much for this.

Here is a solution: https://github.com/orgs/community/discussions/174310#discussioncomment-14474599

My problem is also solve with this: https://github.com/orgs/community/discussions/174310#discussioncomment-14514685

[adisib]

I found a workaround that doesn't involve using any commands. I believe it looked something like this:

1. In the notification center, click "Done" on the sidebar to view all the done notifications
2. Click the checkbox for "Select All", and then click "Move to inbox"
3. Go back to the Inbox and click the checkbox for "Select All". You should see that your number of selected items includes the number of ghost notifications, not just the number moved to inbox
4. Click the "Done" button to mark them as done, which marks the ghost notifications as done as well

[Eliav2]

I had the exact same issue — a ghost notification that wouldn’t disappear. ChatGPT helped me fix it using the GitHub CLI:

# list all unread notifications
gh api notifications

# find the stuck one and delete it
gh api -X DELETE notifications/threads/<notification_id>

After deleting the specific thread (in my case 19198284986), the notification count immediately cleared.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[tigerjack]

The only solution working for me is the one posted here
https://github.com/orgs/community/discussions/6874#discussioncomment-14507162

[gaureshpai]

faced this issue today, not yet resolved :)