\n<\/p>\n
Some Slack users are finding that their notifications aren\u2019t showing up on the platform this morning, or that their corresponding messages are harder to find than usual. A few of my colleagues are reporting similar issues on The Verge\u2019<\/em>s Slack channels, and I\u2019ve been receiving repeated notifications for thread messages that I\u2019ve already marked as read. The issues also seem to be affecting tags for other users \u2014 if a colleague hasn\u2019t responded to your pings, DM them directly for now.<\/p>\n<\/div>\n Slack is aware that \u201cnotifications may be missing for some users\u201d and logged an incident report<\/a> at 7:52AM ET today, later confirming that the issue is impacting threads. \u201cWe\u2019re currently investigating the issue and we\u2019ll be back when we have more information,\u201d Slack announced on its status page. \u201cWe\u2019re sorry for any interruption to your day.\u201d<\/p>\n<\/div>\n It\u2019s unclear what\u2019s causing the disruption to notifications or how many Slack users have been impacted. There\u2019s a visible spike on Downdetector<\/a>, but very few reports have been logged.\u00a0<\/p>\n<\/div>\n For myself, at least, some notifications are coming through, but several minutes after a message has been sent. As of 10:10AM ET, Slack said that \u201cother notifications should be working as expected, but threads may not be loading correctly.\u201d It also logged a separate note<\/a> that reports some users are having trouble adding new members to multi-person DM\u2019s (group chats for up to nine people.)<\/p>\n<\/div>\n