Slack Keeps Showing You as Away While You Work: Causes and Fixes

Slack marks you away for one reason. It has not seen input inside a Slack window for 10 minutes. Typing in Notion, reviewing a pull request, talking in a Zoom call, none of it counts, because Slack only measures interaction with Slack itself.

So the dot is not lying about the rule. The rule is just narrower than your workday. This page lists the causes in order of how often they hit, the tell that identifies each one, and the fix that matches. We build Slack Green, a tool for the last fix on the list, and this page is honest about when you do not need it.

The rule behind the away flip

Three numbers explain almost every case:

• • Desktop and web: you stay active for 10 minutes after your last click,
keystroke, or scroll inside Slack. Input anywhere else on the machine does not reset the timer.
• • Sleep and lock: when the machine sleeps or the screen locks, Slack drops
you to away almost immediately. The 10-minute timer never runs.
• • Phone: the app counts as active only while it is on screen. Background
it and you flip within seconds. Push notifications do not keep you green.

The full per-device table is in how long does Slack stay active, and the deeper detection logic is in how Slack decides when you are away.



Find your cause

You were working in other apps. The most common case. Slack saw no input for 10 minutes because your input went to your editor, browser, or a call. The tell: you flip to away mid-task, roughly 10 minutes after you last touched Slack. This is working as designed, which is exactly the problem.

You were reading. Long thread, spec, ticket. No clicks, no keys, no scroll, no signal. Same mechanism as above, it just feels more unfair.

Your laptop slept or locked. The tell: you go away instantly rather than after 10 minutes, often at the same times every day. Check display sleep, screen lock, and battery saver. Keeping the machine awake stops this particular flip, but note the limit below before installing a keep-awake app.

Your devices disagree. Any signed-in session can hold you green, and the strongest signal wins. A phone that backgrounds Slack, or a desktop that sleeps while the web app stays open elsewhere, produces presence that looks random. The tell: the dot behaves differently on days you use a second device. Sign out of sessions you do not use, or check Slack on mobile behavior.

Your connection dropped. Slack presence rides a WebSocket. A VPN reconnect, captive portal, or aggressive proxy kills it, and you show away until the client reconnects. The tell: away flips that match network changes, not idle time.

You set yourself away and forgot. The manual toggle sticks until you undo it. Check the profile menu first. It happens more than anyone admits.



Fixes that do not work

These come up in every thread about the problem and fail for the same reason. They generate no input inside Slack:

• Keep-awake apps. caffeinate and

Caffeine-style tools prevent the sleep flip, nothing else. You still go away at minute 10.

• Leaving the Slack window open. An open window without input is idle.

• Playing a video. Media playback is not input.

• A status message. Status text and the presence dot are separate systems.

"In a meeting" does not touch the dot, though it does reduce the questions, which is a real if partial win.

• "Set yourself as active". Resets the status once. The timer keeps

running.

Fixes that work

Ordered from free and manual to paid and automatic:

Touch Slack on a rhythm. Click a channel between tasks. Free, and it

trains you to interrupt focus to feed a dot.

Agree on norms instead. If you control the team, say the quiet part:

the dot is not a productivity metric. A written response-time norm beats every tool on this page.

Keep the machine from sleeping. Fixes only the instant-away-on-sleep

cause. Combine with something else for the 10-minute flips.

Simulated input. Jigglers and extensions work while the machine is on

and unlocked, with the caveats covered in Slack Green vs mouse jigglers.

Server-side presence. A service holds your session active from a

server, so the dot follows a schedule instead of your mouse, laptop open or shut. That is what Slack Green does. Every method in this class, including ours, means trusting a service with a session token, so read the security notes first.

The full comparison of every method, with costs and failure modes, is in how to keep Slack active. If your goal is prevention rather than diagnosis, that page and stop Slack from showing away are the next reads.

Frequently asked questions

When does Slack mark you as away? Ten minutes after your last input inside Slack on desktop, seconds after backgrounding the app on a phone, and almost immediately when the machine sleeps or locks.

Why does Slack say I am away when I am active on my computer? Because active on the computer is not active in Slack. Slack cannot see other apps and does not track your mouse outside its own window.

Why does my Slack status keep changing by itself? Multiple sessions. Each device reports separately, and the flip you see is one session going idle or offline while another stays connected.

Does restarting Slack fix a stuck away status? If presence looks wrong for longer than a minute, yes, restart the app or reload the browser tab. A stale WebSocket shows stale presence until it reconnects.

Can my admin see that I use a presence tool? Admins see session metadata, not your input. What they can see, and what your employer might care about, is covered in will I get caught.

The short version

Slack shows you away while you work because it counts only Slack input, and your work happens elsewhere. Identify your cause by the tell: 10-minute flips mean the input timer, instant flips mean sleep or lock, random flips mean a second device or a dropped connection. Fix the machine causes for free, agree on norms if you can, and if the dot still costs you explanations, Slack Green keeps it green on your schedule with nothing running on your laptop.