Slack Stuck on Away? 8 Fixes, In the Order to Try Them
If Slack shows you as away while you're actively typing, the cause is almost always one of three things: a manual away override you set once and forgot, a stale desktop session that stopped reporting activity, or a signed-in mobile device telling Slack you're idle. Work through the list below in order - it's sorted by how often each cause is the real one - and then set up a server-side presence refresh so it never comes back.
How Slack Decides You're Away
Before you troubleshoot, it helps to know what Slack is actually measuring. Presence is not a guess about whether you're working - it's a narrow signal with three inputs:
A 30-minute desktop timer
The desktop client reports activity only when you interact with Slack itself. After 30 minutes with no clicks or keystrokes inside the app, it reports idle and your dot turns gray. Slack offers no setting to change that timeout on any plan, free or paid.
An instant mobile timer
The mobile app flips to away almost immediately when you background it or lock your phone. If mobile is your only connected client, you go gray seconds after switching apps.
A live connection
Presence rides on a persistent WebSocket. Sleep, a dropped VPN tunnel, or a captive Wi-Fi portal severs it, and the server marks you away because nothing is reporting in.
A manual override that wins
If you ever set yourself to away by hand, that choice beats every automatic signal. It sticks across restarts, reinstalls, and devices until you clear it - which is exactly why so many 'stuck' cases are this.
Slack aggregates across all your signed-in clients, so one healthy connection is enough to show green. That's useful to know: it means a stuck away status usually points to an override or to zero healthy connections, not to a bug.
The Fix List, In Order
Do these in sequence. Most people are fixed by step 1 or 2, and steps 7 and 8 are genuinely rare.
- 1.Clear a manual away override
Click your avatar in the top right. If the menu offers "Set yourself as active", you are in manual away mode right now - click it. Manual away is sticky: it survives quitting the app, restarting your machine, and signing in on a new device. Slack will keep you gray indefinitely, which is why this single click resolves more "stuck on away" reports than everything else combined. If the menu already says "Set yourself as away", you're in automatic mode - move on to step 2.
- 2.Fully quit and relaunch the desktop app
Closing the window is not quitting. On macOS use Slack → Quit Slack (Cmd+Q); on Windows right-click the tray icon and choose Quit. A long-running client can end up with a half-dead socket - it renders messages fine but stops sending activity heartbeats, so the server keeps you gray. A clean relaunch rebuilds the connection and usually turns your dot green within seconds.
- 3.Check your other sessions and devices
An old phone, a tablet in a drawer, or a second laptop that is still signed in can keep reporting away. This bites hardest when the desktop client is the one that's misbehaving, because mobile then becomes your loudest signal. Open the mobile app, let it connect, then background it deliberately - or sign out of devices you don't use from your Slack account settings. Also check whether you have the same workspace open in a browser tab that has been suspended by the browser's tab-sleep feature.
- 4.Rule out Do Not Disturb and your notification schedule
DND does not change your presence dot - but it does add a small "z" badge next to your name, and teammates routinely read that as "away". If you set a notification schedule months ago and it starts at 5pm, people will assume you've logged off even while your dot is green. Check Preferences → Notifications and confirm the schedule matches the hours you actually work.
- 5.Test without the VPN, and on a different network
Presence needs a stable long-lived connection. Corporate VPN split-tunneling, aggressive proxies, and hotel or airport captive portals all interrupt WebSockets, and the client silently degrades to a polling mode that reports less. Try disconnecting the VPN for two minutes, or tether to your phone briefly. If your dot goes green off-VPN and gray on-VPN, you've found your culprit and it's a network problem, not a Slack one.
- 6.Sign out of the workspace and back in
This forces a fresh authentication token and a brand-new presence session. It's a heavier hammer than a relaunch and it clears state that a restart won't. Have your workspace URL handy before you do it, and note that you'll need to re-authenticate any SSO login.
- 7.Clear the app cache, then reinstall if needed
In the desktop app use Help → Troubleshoot → Clear Cache and Restart (the exact wording moves around between versions). A corrupted local cache can wedge the client's idea of its own state. If clearing the cache doesn't do it, a clean reinstall of the desktop app is the last client-side step worth taking - and make sure you're on a current version while you're there, since presence bugs do get patched.
- 8.Check status.slack.com
Before you spend another hour on it, load status.slack.com. Slack publishes incidents by feature area, and presence degradations are reported there. If an incident is open, nothing you do locally will help - and if your whole team is showing gray at once, an incident is the likeliest explanation.
A 30-Second Way to Narrow It Down
If you'd rather not run all eight steps, three quick observations will usually tell you where to look:
- Gray even seconds after you type in Slack? That's a manual override (step 1) or a dead session (step 2). Automatic away can never trigger that fast.
- Green for a while, then gray during deep work? That's the ordinary 30-minute idle timer doing its job - nothing is broken, and no amount of troubleshooting will change it. See why Slack shows you as away.
- Gray whenever your screen locks or your laptop lid closes? Expected behaviour. The client can't report activity from a sleeping machine - see keeping Slack active while your computer is locked.
The distinction matters. The first case is a genuine glitch you can fix. The second and third aren't glitches at all - they're Slack working as designed, and the only real answer is to stop depending on your laptop to report your presence.
The Permanent Fix: A Server-Side Presence Refresh
Every step above fixes a stuck status once. None of them stop it recurring tomorrow, because the underlying design hasn't changed: your presence depends on a client that's awake, connected, and being clicked on. Move that responsibility off your laptop and the problem disappears for good.
That's what Slackactivity does. You connect your workspace once with "Continue with Slack", set your work hours, and a cloud cron job calls the official Slack Web API method users.setPresence every 5 minutes inside those hours. Nothing is installed on your machine. Nothing simulates input. It keeps working when your lid is closed, your machine is asleep, or your laptop is switched off entirely.
Runs in the cloud
A 5-minute cron refreshes your presence server-side, so a sleeping laptop, a VPN drop, or a dead desktop session can no longer strand you on away.
Official API, minimal scopes
It requests users:write to set presence and users:read for your account name. It cannot read your messages, files, or channels - there is no scope granted that would allow it.
Unlimited workspaces, one dashboard
Connect as many Slack workspaces as you like, each with its own start hour, end hour, days of the week, and timezone. Vacation mode pauses everything with one switch.
100% free forever
No credit card, no trial countdown, no paid tier waiting to upsell you. Every feature described on this page is free, permanently.
Worth being clear about what this is not: it does not fake work, and it won't make you look busy to anyone paying attention to your actual output. What it does is stop a 30-minute idle timer from broadcasting "offline" while you're heads-down in an IDE, a design tool, or a two-hour call. If you've been reaching for a jiggler instead, compare the two approaches in our mouse jiggler alternative guide, or read the full breakdown of Slack auto-away prevention. Remote teams tend to land here fastest - here's why it matters for remote workers, and the rest of our guides if you want to go deeper.
Frequently Asked Questions
Why is Slack stuck on away when I am clearly active?
The most common cause is a manual away override: if you ever clicked 'Set yourself as away' in your profile menu, Slack keeps you gray forever until you explicitly clear it, no matter how much you type. The second most common cause is a stale desktop session that stopped reporting activity - quitting Slack completely and relaunching fixes it. After that, check whether a signed-in mobile device is reporting away.
How do I clear a manual away status in Slack?
Click your profile picture in the top right of Slack and look at the top of the menu. If it says 'Set yourself as active', you are currently in manual away mode - click it. If it says 'Set yourself as away', you are already in automatic mode and the problem is elsewhere. Manual away persists across restarts and devices, which is why it is the first thing to check.
Does Do Not Disturb make Slack show me as away?
No. Do Not Disturb pauses your notifications and adds a small 'z' badge to your avatar, but it does not change your green/gray presence dot. People often mistake the DND badge for away status. If your notification schedule is on, colleagues may see the 'z' and assume you are offline even though your dot is green.
Why does Slack presence stop updating on a VPN?
Slack presence is maintained over a persistent WebSocket connection. Some corporate VPNs, proxies, and captive Wi-Fi portals interrupt or throttle long-lived connections, so the client stops sending heartbeats and the server falls back to away. Disconnecting the VPN, switching networks, or moving to a different Wi-Fi network usually restores presence within a minute.
How do I stop Slack from going away permanently?
Troubleshooting fixes a stuck status once; it does not stop Slack's 30-minute desktop idle timer from firing again tomorrow. The durable fix is a server-side presence refresh like Slackactivity, which calls the official Slack API every 5 minutes during your configured work hours. It runs in the cloud, so it works with your laptop closed, and it is 100% free forever with no credit card.
The Short Version
- Clear manual away first - it overrides everything and it's the top cause.
- Fully quit and relaunch, then rule out other signed-in devices.
- Check DND, then your VPN or network, then sign out and back in.
- Clear the cache, and check status.slack.com before assuming it's you.
- Then stop it recurring with a cloud presence refresh - free forever, no credit card.
Stop Fixing Your Slack Status by Hand
Connect your workspace, set your hours once, and Slackactivity keeps your presence green through the official Slack API - free forever, no credit card.
