Team members miss urgent direct messages, project blockers sit unanswered, and audio chimes stay silent while the user is looking straight at the screen. When Slack notifications not working problems strike, response times suffer and workplace communication stalls.
Silent notification failures are rarely caused by a simple internet dropout. They usually come from the interaction between Slack’s desktop presence-detection engine, operating-system rules such as Windows Focus Assist, and stale background push registrations.
LEVELZA’s diagnostic workflow therefore triages in order, moving from client preferences to the operating-system notification bridge.
QUICK FIX — SLACK ALERTS NOT ARRIVING
Root Cause Summary: The desktop active-presence timer suppresses alerts, Windows Focus Assist or Do Not Disturb intercepts banners, or the local Electron push notification cache is corrupted.
- Action 1: Set mobile alert timing to send immediately under Preferences > Notifications.
- Action 2: Disable Windows Focus Assist and verify Slack’s permissions in the Windows notification settings.
- Action 3: Run Slack’s built-in notification troubleshooter from Preferences > Notifications.
Escalation Condition: If notifications fail in both the browser and the desktop app, check Slack’s status page for push gateway degradation. Otherwise ask the workspace IT admin about mobile device management (MDM) profile locks.
Why Slack Notifications Stop Working: The Root Causes
Three distinct failure vectors account for most cases on the Slack desktop client. Each one produces the same visible silence, but each is fixed in a different place.
The Desktop Presence-Detection Delay Conflict
Slack continuously tracks mouse and keyboard activity on desktop. When the desktop app registers activity, it marks the user as active and deliberately holds back mobile push notifications to avoid duplicate buzzing.
The problem appears when the desktop app stays open on an unattended laptop. Mobile alerts can then arrive noticeably late, or seem to vanish, until the timing preference is overridden.
Windows Focus Assist and Notification Center Throttling
Windows 10 and Windows 11 both manage notification priority at the system level. Focus Assist, Priority Only, and Do Not Disturb silence desktop banners during full-screen applications, during scheduled hours, or while a display is being mirrored.
Permissions matter as well. If Windows revokes Slack’s background app permissions, banners fail to render even though sound chimes may still play.
Corrupted Push Tokens and Electron Cache Stalls
Slack’s desktop client is built on Electron, and it registers an application identity with the Windows notification system. A stale cache, an abrupt shutdown, or an automatic client update can invalidate that local bridge.
Windows may then drop incoming toast notifications silently, while Slack still treats them as delivered internally. This is why a message can appear in the channel but never trigger a banner.
Step-by-Step Fixes for Slack Notifications Not Working
The four fixes below run from the most common cause to deeper system configuration. Send a test message from another account or device after each one before moving on.
Step 1: Reconfigure In-App Notification Triggers and Mobile Timing
- In the Slack desktop client, click the profile picture and select Preferences, or press Ctrl + ,.
- Open Notifications and confirm Notify me about is set to Direct messages, mentions & keywords. Use All new messages temporarily for testing.
- Scroll to the When I’m not active on desktop section.
- Change the delay drop-down from its default short timer to the option that sends alerts immediately, even when the desktop is active. Exact wording varies by client version.
This forces desktop and mobile alerts to arrive together instead of waiting on the presence timer.
Step 2: Run Slack’s Built-In Notification Diagnostics
- Stay in Preferences > Notifications and scroll to the Troubleshoot section.
- Select the option to launch the notification troubleshooter.
- Let Slack run its automated checks on connectivity, operating-system permissions, and audio output, then send a simulated test alert.
- Read the result. A warning or error beside Windows Notifications means the blockage sits in the operating system, not in Slack.
Step 3: Unblock Slack in Windows Notification Center and Focus Assist
- Press Win + I and open System > Notifications. On Windows 10, also review Focus Assist.
- Confirm the master Notifications toggle is On.
- In the Get notifications from these senders list, find Slack and switch it On.
- Select the word Slack to open its sub-settings. Confirm Show notification banners, Show notifications in notification center, and Play a sound when a notification arrives are all enabled.
- Set Slack’s notification priority to High or Top so alerts can pass through an active Focus Assist or Do Not Disturb session.
If sound plays but no banner appears, the banner option in step 4 is the most likely culprit.
Step 4: Clear the Slack Desktop Cache and Reset App Data
- Open the application menu bar or the hamburger menu in the upper-left corner of Slack.
- Select Help > Troubleshooting > Clear Cache and Restart.
- Slack closes its background processes, purges the stale cache, and restarts.
- If the problem persists, fully quit Slack with Ctrl + Q, press Win + R, and enter
%appdata%\Slack. - Delete the Service Worker and Cache folders to force a fresh registration of the local notification bridge.
- Relaunch Slack, then reopen Settings > System > Notifications and confirm Slack still appears in the Get notifications from these senders list. An app that has lost its registration with the Windows notification system can vanish from that list, so its absence confirms a broken bridge. Send a test message and watch for a banner; if Slack is missing or stays silent, uninstall and reinstall the desktop client to create a clean registration.
Message history lives on Slack’s servers, so clearing local cache does not delete conversations. Sign-in may be requested again afterward. LEVELZA does not recommend editing the Windows registry by hand for this issue, because the sender list exposes the same registration state safely.
When These Fixes Do Not Apply
WARNING — UPSTREAM INFRASTRUCTURE OUTAGES AND ENTERPRISE MDM POLICIES
Client-side troubleshooting cannot resolve delivery failures caused by disruption in Slack’s cloud infrastructure. If Slack’s official status page reports a push notification degradation, no local change will restore alerts until the service recovers.
Corporate devices governed by an MDM profile, such as one deployed through Microsoft Intune or Jamf, may also suppress toast notifications and audio outside defined work hours. Consult the IT department before attempting any registry modification on managed hardware.
If Nothing Above Works: Advanced Escalation
When the four fixes fail, the final step is to hand Slack support real diagnostic data instead of a description of the symptoms.
Use Help > Troubleshooting > Restart with Diagnostics where the client offers it. The resulting logs record how the client behaved during the failure and give support staff something concrete to examine when a ticket is submitted.
Before filing, test in a browser session as well. If the browser also stays silent, the fault sits with the account, the workspace configuration, or Slack’s service.
Administrators who suspect a workspace-wide cause should review organization-wide notification defaults and channel overrides. The guide on How to Set Up a Slack Workspace covers those settings.
