Slack Not Working? 13 Fixes for Notifications, Frozen App & Connection Errors

Notifications went silent, the app is frozen on the loading screen, or Slack has been stuck on "Connecting..." for the last ten minutes. Whatever the symptom, Slack not working is one of the most common productivity-tool complaints we field at IT Cares — and in our support experience, the overwhelming majority of these tickets are not actual Slack outages at all. They trace back to a notification setting overridden somewhere you didn't think to check, or a network that's quietly blocking the real-time connection Slack needs to function.

This guide covers all 13 fixes, ordered from fastest (checking a mute icon) to nuclear (cache wipe, firewall diagnosis, reinstall). We cover desktop (Mac and Windows), browser Slack, and mobile (iOS and Android) separately where the fix differs.

What makes Slack troubleshooting confusing is that the app has more layers of notification logic than almost any other business tool — a global preference, a workspace-wide Do Not Disturb schedule, a per-channel override, plus whatever your operating system and, on mobile, your battery management settings are doing underneath it all. A setting that looks correct at one layer can be silently overridden two layers down, and the app gives you no warning when that happens. That's why so many "Slack is broken" tickets turn out to be a five-second fix once you know exactly where to look.

Which Slack Problem Do You Have?

Symptom	Most Likely Cause	Start With Fix #
Not getting notifications at all	Per-channel mute or Do Not Disturb	1
Notifications work in some channels, not others	Per-channel notification override	2
No notifications on phone only	OS notification permission or battery optimization	6, 12
Stuck on "Connecting..." spinner	Network/firewall blocking WebSocket	9
App frozen, blank, or won't load past splash screen	Corrupted local cache	10
Messages send but don't appear for others	Real Slack incident	8

Not sure which category fits? Start at Fix 1 and work down the list in order — it's built cheapest-and-fastest first, so you'll usually be fixed within the first four or five steps.

13 Fixes for Slack Not Working

On business and enterprise Slack plans, there's a fourth layer worth knowing about: workspace administrators can set organization-wide defaults for certain notification and retention behaviors, and in Slack Connect setups (where two companies share channels between separate workspaces), notification delivery for shared channels can behave slightly differently than for internal channels — messages in a Slack Connect channel sometimes route through a secondary confirmation step the first time a new external contact posts. If notifications work fine in your normal internal channels but not in a shared Slack Connect channel specifically, that's a strong signal the issue is tied to the external-workspace connection rather than anything in your own settings, and it's worth flagging to whichever admin manages the Slack Connect relationship on your side.

Why "Connecting..." Doesn't Mean Slack Is Down

Many users assume a stuck "Connecting..." spinner means Slack's servers are having problems. In our support experience, that's rarely the case — it almost always means your network is blocking part of what Slack needs to function, while allowing enough traffic through that the app appears to partially load.

Here's what's actually happening: Slack's interface (buttons, sidebar, channel list) loads over standard HTTPS, which almost every network allows. But real-time message delivery depends on a persistent WebSocket connection (wss://) that many corporate firewalls and some VPN clients block by policy, either intentionally (security hardening) or as an unintended side effect of deep packet inspection. The result: the app "loads" — you see the interface — but it never actually connects, and the spinner never resolves. The fix isn't on Slack's end; it requires your network administrator to allowlist outbound WebSocket traffic to *.slack.com.

How Slack's Layered Notification System Actually Works

Understanding why notifications fail requires understanding that Slack checks several independent settings, in order, before it decides whether to alert you. Think of it as a chain — if any single link says "no," the notification is suppressed, regardless of what the other links say:

• Channel-level: Is this specific channel muted, or does it have a custom notification preference that overrides the workspace default?
• Workspace-level: Is Do Not Disturb (Pause notifications) currently active for this workspace?
• App-level (global): Does your Preferences > Notifications setting even allow this type of message ("All new messages" vs. "Direct messages, mentions & keywords" vs. "Nothing")?
• Operating-system level: Does macOS or Windows have Slack's app-level notification permission enabled, and is a Focus mode or Focus Assist profile currently filtering it out?
• Device level (mobile only): Is the app allowed to run in the background, and is battery optimization letting it maintain a live connection to receive push notifications at all?

Because there are five potential points of failure and Slack doesn't surface a unified "here's why you didn't get notified" diagnostic, the fastest troubleshooting approach is to walk the chain from the most specific layer (channel) to the most general (device/OS) — which is exactly the order Fixes 1 through 6 in this guide follow.

Desktop vs. Browser vs. Mobile Slack — What's Different

The three main ways people use Slack each have a distinct failure mode, which is why a fix that works on desktop sometimes does nothing for the same problem on mobile.

Desktop app (Mac/Windows): Runs as a persistent background process, so it maintains a constant connection to Slack's servers. Problems here are usually either a corrupted local cache (frozen/blank window) or an OS-level notification permission that got reset after a system update. Desktop is also the only version affected by SMC-style or Focus-mode quirks tied to the operating system itself.

Browser Slack: Runs only while the tab is open, and depends on the browser's own notification permission system in addition to Slack's. Background tab throttling — a power-saving feature in every modern browser — can delay notification delivery by several seconds to a couple of minutes if the tab hasn't been active recently. Browser Slack is generally the least reliable option for real-time alerts and is best treated as a backup rather than a primary client for anyone who depends on instant notifications.

Mobile (iOS/Android): Relies on push notifications delivered through Apple's or Google's push infrastructure even when the Slack app itself isn't actively running — which is precisely why battery optimization settings matter so much on Android. If the OS decides Slack shouldn't be allowed to maintain any background presence, push notifications can silently stop arriving with zero error message on either end. iOS is generally more consistent here because Apple's push notification service doesn't depend on the app staying "awake"; Android's behavior varies more by manufacturer (Samsung, Xiaomi, and OnePlus phones are historically more aggressive about killing background apps than stock Android).

Preventing This From Happening Again

Once you've fixed the immediate problem, a few habits prevent the most common recurrences:

• Periodically review muted channels — Slack doesn't remind you which channels you've silenced, so a quick monthly check (right-click each channel > Notification preferences) catches forgotten mutes before they cause a missed deadline.
• Bookmark status.slack.com so "is it just me or is Slack down" takes ten seconds to answer instead of an hour of troubleshooting.
• On Android, re-check battery optimization settings after major OS updates — manufacturers sometimes reset app-specific battery permissions during system upgrades.
• If you work on a corporate network with a restrictive firewall, ask IT to proactively allowlist Slack's WebSocket endpoints rather than waiting for the next "Connecting..." incident.
• Keep the desktop app updated automatically (Slack does this by default) so you're never troubleshooting a bug that was already patched two versions ago.

Common Slack Error Messages and What They Actually Mean

A few recurring error messages account for most of the confusion. Here's what each one actually indicates:

"You are not connected to the internet" — This banner can appear even on a working connection if Wi-Fi drops for a fraction of a second, or if your laptop briefly switches between networks (common when moving between rooms on mesh Wi-Fi, or waking from sleep). It usually self-resolves within a few seconds. If it appears repeatedly and persistently rather than as a brief flash, treat it as a genuine connectivity problem and test your network directly.

"Something went wrong" (generic error screen) — This is Slack's catch-all error when the app hits an unexpected state it can't recover from gracefully. It's almost always resolved by Fix 10 (clearing the local cache) — the underlying cause is nearly always corrupted local data rather than a server-side problem.

"This workspace does not exist" — Appears when you try to open a workspace URL that's been renamed by an admin, when you've been removed from a workspace, or when you've simply mistyped the workspace subdomain (e.g. yourcompany.slack.com). Double-check the URL and confirm with a colleague that the workspace is still active and that your account hasn't been deactivated.

Blank, gray, or white screen on launch — Functionally the same underlying cause as a frozen app: a corrupted cache or a failed app update. Go straight to Fix 10 (cache clear) or Fix 11 (reinstall) rather than waiting for it to resolve itself.

A flickering "Reconnecting..." banner (as opposed to a static "Connecting..." that never changes) — This indicates an unstable connection rather than a fully blocked one: the WebSocket connects, drops, and reconnects repeatedly. This points to intermittent packet loss or an unstable Wi-Fi signal rather than a hard firewall block, and is best diagnosed by testing on a wired connection or a different network entirely.

When to Fix It Yourself vs. Escalate to IT

Fixes 1 through 8 (notification settings, Do Not Disturb, Focus modes, browser permissions, and checking status.slack.com) are entirely within any user's control and typically take under five minutes combined. Fixes 10 and 11 (cache clearing, reinstalling) are also safe for most users to attempt solo, though they do require signing back in afterward.

Fix 9 — diagnosing a firewall or WebSocket block — is different: on a personal home network you can usually resolve it by restarting your router or switching to a different DNS provider, but on a corporate or school network, this genuinely requires your network or IT administrator to make a change to firewall rules. There's no user-side workaround for a network that's deliberately blocking WebSocket traffic by policy. If you've confirmed the problem is network-side (Slack connects fine on your phone's mobile hotspot but not on the office Wi-Fi), escalate directly to IT with that specific finding — it saves them a diagnostic step and gets you unblocked faster.

Frequently Asked Questions

Why am I not getting Slack notifications even though they're turned on?

The most common cause is a notification setting overridden at a more specific level than you're checking. Slack has three layers: global (Preferences > Notifications), per-workspace (Do Not Disturb / Pause notifications), and per-channel (mute icon or a custom preference set on that one channel). Even if your global setting is "All new messages," a muted channel or an active Do Not Disturb schedule will silently block alerts. Also check OS-level notification permissions and, on Mac, whether a Focus mode is filtering Slack out.

Why is Slack stuck on "Connecting..." and never loads?

A persistent "Connecting..." spinner is almost always a network problem, not a Slack account problem. Slack needs outbound HTTPS (port 443) access to *.slack.com plus an open WebSocket (wss://) connection for real-time messages. Corporate firewalls, some VPNs, and public Wi-Fi captive portals block WebSocket traffic even though normal web pages load fine. Check status.slack.com first to rule out an outage, then try a different network to confirm it's network-side.

How do I clear Slack's cache on Mac and Windows?

Fully quit Slack first. On macOS, the cache is at ~/Library/Application Support/Slack. On Windows, it's at %appdata%\Slack. For a lighter fix, delete only the "Cache" and "Service Worker" subfolders to keep local search history intact. For a full reset, delete the entire Slack folder — this signs you out and forces a fresh resync, resolving most sync and rendering glitches.

Why aren't Slack notifications showing up on my phone?

On iOS, check Settings > Notifications > Slack and confirm Allow Notifications is on. On Android, the most common cause is battery optimization: if Slack's battery usage is set to "Restricted" or "Optimized," Android kills its background connection and notifications stop arriving. Go to Settings > Apps > Slack > Battery and set it to "Unrestricted." Also check Do Not Disturb schedules on the device itself.

Is there a real Slack outage happening right now?

Check status.slack.com — Slack's official public status page with real-time incident reports. If it shows all green and only you are affected, the problem is local. In our support experience, the overwhelming majority of "Slack is down" tickets turn out to be a local notification or network misconfiguration rather than an actual outage.

How do I tell whether a missing notification is a Slack setting or an operating system setting?

Test in this order: first, send yourself a test direct message from another account or ask a colleague to message you directly (this bypasses per-channel mute settings). If you get no desktop banner at all, temporarily disable any active macOS Focus mode or Windows Focus Assist profile and try again — if the notification now appears, the OS was the cause. If it still doesn't appear, open Slack Preferences > Notifications and confirm the global setting isn't set to "Nothing." Isolating each layer one at a time is faster than guessing, since Slack itself doesn't tell you which layer blocked a given notification.