The most useful first step when Slack is not working is checking whether Slack itself is having problems, because a meaningful fraction of “Slack not working” experiences are actual service outages on Slack’s side rather than problems with your computer or account. Most troubleshooting articles skip this and lead with restart-and-clear-cache steps that waste your time when the underlying issue is that Slack’s infrastructure is having problems. Five minutes saved by checking service status first compounds across the many times you will inevitably troubleshoot Slack issues over years of use.
This matters because Slack outages happen with enough regularity that “user-side problem versus Slack-side problem” is a real diagnostic question. Slack has had multiple substantial outages in recent years, and partial outages affecting specific features (file uploads, calls, search) happen more frequently than full outages. Knowing how to quickly distinguish “Slack is broken right now” from “my installation has a problem” prevents wasted troubleshooting effort on issues you cannot fix from your end.
This guide is structured to check service status first, then move through troubleshooting layers from most likely to least likely cause. For broader context on the troubleshooting and fixes catalog, our complete guide to fixing errors covers the approach across many tool categories.
Step 1: Check Slack Service Status Before Anything Else
Before troubleshooting your own setup, verify whether Slack itself is operating normally. This takes 30 seconds and saves substantial time when the answer is “Slack is having problems.”
Visit slack.com status page directly through your browser. Slack publishes incident reports for ongoing outages, recently resolved issues, and historical incidents. Active incidents are clearly marked, and the status page indicates which Slack features are affected. If your specific issue (messages not sending, calls failing, search not working) matches an active incident, the realistic response is to wait for Slack to resolve it rather than troubleshooting your setup.
Cross-reference with third-party outage tracking. Sites like downdetector.com aggregate user reports of service issues across many services including Slack. A sudden spike in user-reported issues typically indicates real service problems even before Slack’s own status page acknowledges them. If many other users are reporting the same problem you are experiencing, the issue is likely on Slack’s side.
Check with colleagues directly. If others on your team are using Slack normally while you are not, the issue is more likely on your side. If multiple team members are experiencing the same problem simultaneously, the issue is more likely on Slack’s side or specific to your workspace’s configuration. This human check is often the fastest diagnostic — direct messages to colleagues through other channels (email, Microsoft Teams if you have it, phone) clarify the situation quickly.
If service status confirms a Slack-side outage, the appropriate response is waiting for resolution rather than troubleshooting. The temptation to try fixes anyway often produces fake successes — the issue resolves on Slack’s side at roughly the same time you try a fix, leading you to incorrectly conclude that the fix worked. Wait for Slack’s status page to mark the incident resolved before resuming.
If service status appears normal and the issue is only affecting you (or a small group), proceed to the user-side troubleshooting below.
Step 2: App Will Not Load or Is Stuck
If the Slack desktop app fails to launch, hangs on the loading screen, or shows a blank window, the issue is typically with the local app rather than with Slack’s service or your account.
Force quit and restart the app first. On Windows, Task Manager (Ctrl+Shift+Esc) → find Slack in the Processes tab → End Task → then relaunch. On Mac, Cmd+Option+Esc → select Slack → Force Quit → then relaunch. The simple restart resolves a substantial fraction of transient app problems.
Restart your computer if the app restart did not help. Some Slack issues are caused by other system state that a computer restart clears. The 30 seconds for a restart is worth trying before more elaborate troubleshooting.
Clear the Slack cache if restart did not work. On Windows: close Slack completely, then navigate to %APPDATA%SlackCache and delete the contents (not the folder itself). On Mac: close Slack, then navigate to ~/Library/Application Support/Slack/Cache and delete the contents. After clearing cache, relaunch Slack. This resolves issues caused by corrupted cached data.
Reinstall the app if cache clearing did not help. Uninstall Slack through Windows Settings → Apps (or drag from Applications to Trash on Mac), then download a fresh installer from slack.com/downloads, and reinstall. The reinstall produces a clean installation that resolves issues caused by corrupted application files.
Try the web version at slack.com if the desktop app continues to fail. The web version uses different code paths and connections than the desktop app; success in the browser while the app fails indicates the app is the problem rather than your account or network. Using the web version is a viable workaround while resolving the app-specific issue.
For specific load failures with error messages, the error text often points to specific causes. Network errors suggest connectivity problems (check the next section). Authentication errors suggest account issues (handled later). Generic errors with no specific message warrant the standard restart-cache-reinstall sequence above.
Step 3: Notifications Not Arriving
The most common Slack issue users report is notifications not appearing reliably. This is genuinely complex because Slack notifications depend on several systems working correctly together — Slack’s notification delivery, your operating system’s notification handling, your specific application notification settings, and various Do Not Disturb or focus mode settings that can suppress notifications.
Start with Slack’s notification settings within the app. Slack → Preferences → Notifications shows what events trigger notifications and what notification methods are used. Verify that you have notifications enabled for the categories you care about (direct messages, mentions, all messages depending on preference). Channel-specific notification settings can override these — right-clicking a channel and checking notification preferences reveals if a channel has been muted or has reduced notifications.
Check operating system notification permissions. Windows Settings → System → Notifications → Slack must have notifications enabled. Mac System Settings → Notifications → Slack similarly. If Slack does not have system notification permission, no in-app setting will make notifications appear.
Check Do Not Disturb and Focus mode states. Windows Focus Assist and Mac Focus modes both suppress notifications based on schedules or manual activation. The “missing notifications” sometimes turn out to be suppressed by a focus mode you forgot was enabled. Disable focus modes temporarily to verify whether notifications appear when they are not suppressed.
Check Slack’s notification schedule. Slack → Preferences → Notifications → Notification Schedule may be set to limited hours, suppressing notifications outside those hours. Verify the schedule matches your actual needs.
For users on Mac specifically, the notification permission state can become inconsistent in ways that require resetting. Mac System Settings → Notifications → Slack → toggle notifications off, wait a moment, toggle back on. This sometimes resolves cases where notifications were silently disabled despite appearing enabled.
If individual notifications are arriving but with no sound, check Slack’s sound settings (Preferences → Notifications → Sound) and your system volume. Notification sounds can be disabled at multiple layers, and silent notifications are often misinterpreted as “missing notifications.”
For users who specifically need reliable urgent notifications, the realistic recommendation is verifying the entire notification chain — Slack settings, OS permissions, focus mode state, sound settings — rather than trying single fixes. Slack notifications failing is rarely about a single setting; it is usually about one layer in the chain being misconfigured.
Step 4: Cannot Send Messages or Messages Failing
When messages fail to send (showing pending indicators, error states, or simply not arriving for recipients), the cause is usually one of several specific scenarios.
Network connectivity issues prevent message sending. The first check is whether your internet connection is working — load any web page in your browser, ideally a site not on Slack’s infrastructure, to verify connectivity. If general internet works but Slack does not, the issue is more specific.
Corporate networks sometimes block Slack-specific traffic. Some corporate firewalls explicitly block Slack, particularly at companies that prefer Microsoft Teams or other alternatives. If you are on a corporate network and Slack is not working while other things do, contact your IT department about Slack access. Switching to a personal network (phone hotspot, home wifi) can verify whether the corporate network is the issue.
VPN connections sometimes interfere with Slack. The VPN may route Slack traffic through paths that produce reliability issues, particularly for international VPN connections. Try disconnecting your VPN temporarily to see if Slack works without it. If yes, the VPN configuration is the issue, and the VPN provider’s support or different server selection may resolve it.
Workspace-specific issues affect message sending in specific contexts. If you can send messages in some workspaces but not others, the issue is specific to the failing workspace. Common causes include posting permissions for guests or external members, channel-specific restrictions, or workspace-level configuration changes that your admin made.
Message size limits matter for specific situations. Very long messages, messages with many embedded files, or messages with complex formatting can fail when smaller messages succeed. Try sending shorter test messages to isolate whether size is the issue.
Account permissions matter for restricted workspaces. Some workspaces restrict who can post in specific channels, who can mention @channel or @everyone, or other actions. Permission denials sometimes appear as silent failures rather than clear error messages. Check with your workspace admin if you suspect permission issues.
For specific persistent message sending failures, contacting Slack support through the failing workspace produces appropriate help. The support team has visibility into account-specific and workspace-specific issues that no general troubleshooting can address. Our Microsoft Teams troubleshooting guide covers the related category for users in mixed Slack and Teams environments.
Step 5: Calls and Huddles Not Connecting
Slack calls and huddles have additional dependencies beyond regular messaging. When calls fail while text messaging works, the cause is usually related to audio, video, or specific networking requirements that calls need.
Browser permissions for camera and microphone affect calls in the Slack web app and may affect the desktop app on some platforms. Verify that Slack has permission to access camera and microphone in both your operating system settings and the Slack app’s preferences.
Audio device selection matters when you have multiple devices (built-in microphone plus external headset, multiple speakers). Slack’s call settings (during a call or in Preferences → Audio & Video) let you select specific input and output devices. The default selection may not be what you expect — particularly after connecting or disconnecting headphones, Bluetooth devices, or other audio hardware.
Network bandwidth affects call quality and reliability. Calls require sustained bandwidth for both upload (your video and audio to others) and download (others’ video and audio to you). Networks that handle messaging fine may struggle with calls if they are bandwidth-constrained or experiencing congestion. Testing your network speed (fast.com or speedtest.net) reveals whether bandwidth is genuinely limiting.
Corporate firewalls sometimes specifically block call traffic while allowing chat. The protocols and ports used for real-time calls differ from messaging, and corporate network policies sometimes treat them differently. If you can chat but not call, network configuration is a likely cause.
For calls that connect but have audio or video problems (echo, distortion, freezing, one-way audio), the troubleshooting becomes more specific to the affected media. Echo suggests microphone-speaker feedback that headphones resolve. One-way audio suggests permissions or device selection issues. Freezing suggests bandwidth or processing issues. Our Zoom audio troubleshooting guide covers the broader category of video call audio issues with detailed coverage.
Step 6: Search Not Working or Producing Wrong Results
Slack search problems are usually one of several specific scenarios.
Search results take time to update after new messages are sent. Slack does not index messages instantly — there is often a delay of minutes or longer between message posting and the message being searchable. If you are searching for something very recent, waiting and retrying often resolves the apparent search failure.
Search scope limits matter. Slack’s free workspaces have limited message history (90 days of accessible history with up to 90 days searchable in current free tier), and searches do not return results older than the accessible window. If you are searching for older content, the limitation is the workspace’s plan tier rather than search functionality.
Search syntax matters for finding specific content. Slack supports specific search operators (from:@user, in:#channel, before:date, after:date, has:link, has:pin, others) that significantly affect results. Searches that return nothing useful often work when reformulated with specific operators. Slack’s search help documentation covers the operators available.
Caching of search results sometimes produces stale results that do not reflect the current workspace state. Reloading the Slack window (Ctrl+R on Windows, Cmd+R on Mac in the desktop app) refreshes the search index in your local app and may resolve apparent search problems.
For persistent search problems where results are clearly wrong, the issue may be account-level or workspace-level rather than user-side. Slack support can investigate search-related issues with visibility that general troubleshooting cannot match.
Step 7: Account and Sign-In Issues
For issues that point to your account specifically (cannot sign in, signed out repeatedly, getting authentication errors), the troubleshooting focuses on account state.
Sign in through the web at slack.com if the desktop app fails to authenticate. The web sign-in process gives more detailed error messages than the desktop app sometimes provides, and successful web sign-in indicates the account is functional even if the desktop app has issues.
Two-factor authentication issues sometimes prevent sign-in if your authentication method is unavailable. If you use authenticator apps and have lost access to the device with the authenticator, your workspace admin can help recover access. If you use SMS-based 2FA and have a new phone number, similar recovery procedures apply.
Workspace removal happens occasionally — admins remove members who have been inactive, members who have left organisations, or as part of workspace cleanup. If a workspace you used to be in is no longer accessible, contacting the workspace admin or owner confirms whether your access was removed.
SSO (Single Sign-On) issues for organisations using identity providers can prevent Slack sign-in. These issues are usually visible in your organisation’s identity management system rather than in Slack directly. If you cannot sign in to Slack at your workplace and your organisation uses SSO, IT support is the appropriate response.
For users with multiple Slack workspaces, sometimes specific workspace issues require signing out and back into that specific workspace within the Slack app. Right-click the workspace icon in the Slack app sidebar for sign-out options that affect only that workspace. Our Discord troubleshooting guide covers a similar pattern of platform-specific authentication issues in the related chat platform category.
The Practical Recommendation
For most users in 2026 experiencing Slack issues, the answer is to follow the troubleshooting sequence from service status check downward. Step 1: Check Slack service status (slack.com status page, downdetector.com, ask colleagues) — most “Slack not working” experiences are real outages and waiting is the right response. Step 2: Restart the app, clear cache, reinstall if persistent — handles most app-specific issues. Step 3: Verify notification chain across Slack settings, OS permissions, focus modes — fixes most “missing notifications” issues. Step 4: Network connectivity, corporate firewall checks, VPN interference — addresses most message sending failures. Step 5: Device permissions, audio device selection, bandwidth checks — handles most call problems. Step 6: Search timing, scope limits, syntax operators — clarifies most search confusion. Step 7: Web sign-in, 2FA recovery, workspace admin contact, SSO issues — addresses authentication problems. The wrong move is jumping to elaborate fixes without first verifying whether Slack itself is having problems, because fixing nothing wrong on your side wastes time when the issue resolves on Slack’s side. Check service status first, work through the layers from most likely to least likely cause, and the troubleshooting becomes systematic rather than random. Our team chat apps comparison covers the broader category that includes alternatives users sometimes evaluate during recurring Slack issues.
