Why Slack Presence Gets Stuck
Slack determines your presence from a narrow set of signals — primarily interaction within the Slack app window itself. This means:
- Moving your mouse in another application does not reset the Slack inactivity timer.
- Typing in a document editor does not keep you Active in Slack.
- Being on a Zoom call does not signal Active to Slack.
Slack marks you Away after 10 minutes of no Slack-specific activity on desktop. After extended inactivity across all devices, it marks you Offline. Neither is a bug — it's by design. But it creates the frustrating situation where you're clearly at your computer, and Slack tells your team you've vanished.
Six Fixes for Stuck Slack Presence
Set yourself as active manually
Click your profile picture → Set yourself as active. This resets your status to Active immediately. It's the fastest fix but doesn't solve the underlying problem — you'll go Away again after another 10 minutes without Slack activity.
Check that Slack is your focused window
Slack's inactivity timer only pauses when Slack is the active foreground window. If you've been reading a document all morning with Slack open in the background, the timer ran the whole time. Click into the Slack window to reset it.
Disable Do Not Disturb / check notification snooze
A DND moon icon or active Notification snooze won't cause Away status — but some Slack integrations behave unexpectedly when DND is on. Go to your profile → Pause notifications → check if it's active and whether it was set with an unintended long duration.
Force-quit and relaunch Slack
On Mac: Cmd+Q (not just closing the window). On Windows: right-click Slack in the system tray → Quit. Then relaunch. This forces a fresh WebSocket connection with Slack's servers and re-establishes presence signalling from a clean state.
Force-quit the mobile app
If your phone has the Slack app and it went to the background while you were Away, the mobile session can hold a stale Away or Offline status. Force-close the Slack mobile app on iOS or Android. The server then relies solely on your desktop session.
Sign out and sign back in
Go to Slack → your workspace name → Sign out. This terminates the presence session entirely. When you sign back in, Slack re-registers your client and presence updates fresh. Use this if Fix 04 didn't resolve the issue.
Symptom-to-Fix Reference
| Symptom | Likely Cause | Best Fix |
|---|---|---|
| Away after 10 min at desk | Working in another app, not Slack | Fix 01 / cloud tool |
| Shows Offline despite app open | WebSocket connection dropped | Fix 04 Restart Slack |
| Flickers Active/Away repeatedly | Mobile app conflict | Fix 05 Force-quit mobile |
| Away despite active Slack window | Stale presence session | Fix 06 Sign out/in |
| Correct for you, wrong for colleagues | Propagation delay | Wait 60–90 seconds |
| Goes Away constantly despite being at desk | Inactivity timer — by design | Use a presence tool |
The Real Problem: Slack's Inactivity Timer Is Working Correctly
If your presence keeps going Away when you're at your desk but not actively using Slack, the six fixes above won't give you a permanent solution — because the inactivity timer is working exactly as designed. You're just not meeting Slack's definition of "active."
What counts as Slack activity:
- Typing in a message composer
- Clicking between channels or DMs
- Scrolling through a channel
- Reacting to a message
- Using Slack's search
What doesn't count:
- Slack open in the background while you work in other apps
- A meeting in Slack Huddles (presence can still go Away)
- System mouse movement
- Typing anywhere except inside Slack
If you need your green dot to stay lit regardless of what you're doing, the only reliable options are to interact with Slack regularly, or use a cloud-based tool that maintains your Active status without local activity. See our guide on keeping Slack active automatically for a full comparison.
When Slack Shows Offline (Not Just Away)
If Slack shows you as Offline — no dot, or a hollow grey dot — the client has lost its connection to Slack's servers. This usually resolves itself, but if it persists:
- Check your internet connection (try loading a webpage).
- Check status.slack.com for active incidents.
- If on a corporate network, check whether a VPN or proxy is blocking the WebSocket connection Slack uses for real-time updates.
- Restart Slack (Fix 04).
Corporate network proxies are a surprisingly common cause — particularly after a VPN connection drops and reconnects, leaving the Slack session in a half-connected state.