Your notification toggle is on. You double-checked it. And yet a message someone sent at 9 a.m. buzzes your phone at lunch, or only shows up the moment you wake the screen. This is one of the most maddening tech problems of 2026 because everything looks correctly configured. The truth is that a delayed alert almost never means Slack is broken. It means something between Slack and your device decided the message could wait: an Android battery rule, an iPhone Focus schedule, or a desktop session that told your phone to stand down. The fix is not one switch. It is figuring out which layer is holding your alerts, then clearing that layer. Here is how to do that on every device, sorted by the exact symptom you are seeing.

Fix It Fast: if Slack alerts arrive on but late, the culprit is usually device power management, not Slack. On Android, set Slack to Unrestricted battery use and turn off Adaptive Battery. On iPhone, check Focus, Low Power Mode, and Scheduled Summary. On both, remember that an open laptop makes Slack delay mobile pings on purpose. Match the fix to the pattern: alerts only when you wake the phone points to battery limits, alerts only on WiFi points to background data restrictions, and alerts that vanish on a schedule point to a Focus mode.

The reason this feels so confusing is that the notification toggle only controls whether Slack is allowed to alert you. It says nothing about whether your device chooses to deliver that alert right away. A modern phone or laptop runs an aggressive power and attention manager that sits between Slack and your screen, and that manager is allowed to hold a notification for minutes or hours if it thinks you do not need it yet. So the alert was sent on time. It simply sat in a queue your operating system controls. Once you see the problem this way, the fix stops being “reinstall Slack” and becomes “find the thing that is queuing my alerts and tell it to stop.” That thing is almost always one of three suspects: Android battery optimization, an iPhone Focus or Low Power setting, or a desktop Slack session that changes how your phone gets pinged.

Delayed notifications are not all the same problem, and the exact pattern tells you where to look. Before you change any setting, watch the behavior for a day and match it to the table below. This saves you from disabling five things at once and never learning what actually fixed it.

If you use an Android phone, start here, because aggressive battery management is the single most common reason work alerts land late. Android sorts every app into a battery tier, and an app in a restricted tier gets its background network access throttled, which is exactly the connection Slack needs to receive a push in real time. The fix is to lift Slack out of that tier. Open Settings > Apps > Slack > Battery and set it to Unrestricted, or toggle on Allow background activity. That one change resolves a large share of “late Slack” complaints on phones running Android 12 through Android 16.

The second Android suspect is Adaptive Battery. It learns which apps you use and quietly delays background work for the ones it thinks you use less, and it does not care that the delayed app is your job. Pixel owners in particular report alerts arriving twelve or more hours late until they open Settings > Battery > Adaptive Battery and switch it off. Underneath both settings sits Android’s Doze mode and App Standby, which batch background jobs while the phone is idle, as Google documents in its Doze and App Standby guide. If your alerts consistently appear the second you wake the phone, that is Doze holding them until the device is active. This is the same family of power behavior behind our fixes for Android 16 battery drain after updating, which is worth a read if aggressive power saving started after a recent update.

Stock Android is only half the story. Phone makers layer their own battery managers on top, and several of them are far more aggressive than Google’s defaults. Samsung’s One UI has a “Put unused apps to sleep” feature and a deep sleeping apps list that can strangle Slack in the background. Xiaomi and its HyperOS builds control background permission through Autostart and a per-app battery saver that must be set to No restrictions. OnePlus, Oppo, and others ship similarly heavy schemes. The clearest reference for the exact steps on each brand is the community-run Don’t Kill My App project, which documents where each manufacturer buries these controls. The pattern is always the same: find the maker’s autostart or app-sleep list and mark Slack as allowed to run and never put to sleep.

On iPhone the cause is usually intentional delivery control rather than a battery tier. A Focus mode such as Work, Sleep, or Do Not Disturb can silence Slack during set hours, and a Focus filter can hide it entirely, so the alert is delivered but not shown until the Focus ends. Low Power Mode adds its own drag by throttling background activity, which can delay a push until you next open the phone. And Scheduled Summary quietly bundles chosen apps into a batch that arrives at fixed times. Check Settings > Focus for any active schedule, confirm Slack is left out of Settings > Notifications > Scheduled Summary, and see whether Low Power Mode kicked in when your battery ran low. Because the iPhone side has several distinct layers, we cover them step by step in our dedicated guide to Slack notifications delayed on iPhone, including the in-app notification test.

Here is a rule that surprises almost everyone. Slack deliberately holds your mobile alert while it thinks you are active at your computer. By default it waits one minute after your desktop screen locks, or ten minutes after it stops detecting cursor activity, before it hands the notification to your phone. That behavior is handy when you are moving between desk and pocket, and it is infuriating when your laptop is open on a side table and Slack assumes you are reading. If your phone only lags while your computer is on, this is almost certainly why. You can shorten the wait inside Slack by opening Notifications, tapping Notify Me on Mobile, and choosing As soon as I’m inactive. Slack’s own notification troubleshooting guide points to the same setting, and it also runs a built-in delivery test worth trying before you touch anything drastic.

The reverse problem happens on the desktop side. On a Mac, App Nap can throttle a Slack window that has been in the background for a while, especially when Slack is running as a browser tab rather than the standalone app, so notifications arrive late or without sound. Keeping the dedicated Slack app open and in view is more reliable than leaving it buried behind other windows. On Windows, Focus Assist (and its Quiet Hours cousin) can suppress banners and mute sounds even when Slack looks configured correctly, so check Settings > System > Focus and confirm Slack is a priority app. Remember that the desktop and mobile layers interact: because Slack routes to your phone based on desktop activity, a laptop that keeps waking to sync can reset the inactivity timer and keep your phone quiet longer than you expect. If your wider issue is other work apps misbehaving too, our walkthrough for Teams camera problems in meetings shows the same “check the OS layer before blaming the app” approach.

Two specific patterns point straight at their cause. If Slack alerts are punctual on WiFi but late or missing on cellular, the problem is background data. Android lets you restrict an app’s mobile data, and Data Saver can throttle background connections network-wide, both of which choke the push channel Slack relies on. Open Settings > Apps > Slack > Mobile data and allow background data usage, then confirm Data Saver is off or that Slack is exempt. A VPN or a DNS-level content filter can also block push traffic on cellular while leaving WiFi untouched, so test with the VPN off. The other clue is alerts that appear only after you wake the phone, which is the fingerprint of battery optimization parking the push until the device is active. This is the same category of delayed-delivery trouble behind 2FA codes not arriving and RCS messages not being delivered, and the diagnostic instinct is identical: separate the message from the delivery layer.

Once in a while the app is the problem, and 2026 brought a specific version of it worth knowing. Android users have reported that when a desktop Slack session for the same account auto-starts and sits in the background, their phone notifications get dismissed almost the instant they arrive, as if the desktop grabbed and cleared them. If your alerts show up and then disappear within a second or two, fully quit the desktop Slack app rather than closing its window, and sign out of any auto-launched session, then watch whether mobile delivery returns to normal. It is also worth running Slack’s own Troubleshoot Notifications test from your profile, since that separates a device-side delay from an actual account or install issue. If sound is your real complaint rather than timing, our fix for Slack huddle audio not working covers the related permission tangle.

That timing is the classic signature of battery optimization. Doze mode and Adaptive Battery on Android, or Low Power Mode on iPhone, hold background pushes while the device is idle and release them the moment you wake the screen. Set Slack to Unrestricted battery use, turn off Adaptive Battery, and disable Low Power Mode to get alerts in real time.

Because background data on cellular is being restricted. Android can limit an app’s mobile data, and Data Saver throttles background connections across the phone, both of which delay Slack’s push channel. Allow background data for Slack, turn off Data Saver or exempt Slack, and test with any VPN or DNS filter switched off.

Yes, by design. Slack waits about one minute after your desktop locks, or ten minutes after it stops seeing cursor movement, before pushing to your phone. If your phone only lags while your computer is on, set Notify Me on Mobile to As soon as I’m inactive, or fully close the desktop app when you step away.

The impact is usually small for a chat app that already runs in the background. Setting one important app to Unrestricted lets it keep a live connection so alerts arrive on time, and most users see no meaningful battery hit. If you are cautious, exempt only the few apps whose alerts you cannot afford to miss rather than disabling optimization system-wide.

On Android this has been linked to a background desktop Slack session for the same account, which can dismiss mobile pushes as they arrive. Quit the desktop app completely, sign out of any auto-launched session, and retest. If it continues, run Slack’s built-in Troubleshoot Notifications test to check for an account or install problem.

• Watch the pattern first: only-on-wake means battery, only-on-cellular means background data, only-on-schedule means a Focus mode.
• On Android, set Slack to Unrestricted battery, turn off Adaptive Battery, and clear the maker’s app-sleep or autostart list.
• On iPhone, check Focus schedules, Low Power Mode, and Scheduled Summary before anything else.
• Remember the desktop handoff: an open laptop makes Slack wait to ping your phone, so set Notify Me on Mobile to As soon as I’m inactive.
• If alerts flash and vanish, quit the desktop app fully, then run Slack’s Troubleshoot Notifications test before reinstalling.

A Slack alert that arrives three hours late is not a mystery once you stop treating it as one broken switch. It is a queue somewhere between the message and your screen, and in 2026 that queue almost always lives in your device’s power or attention manager rather than in Slack. Read the symptom, aim at the right layer, and clear it: battery tier for phone-wake delays, background data for cellular-only delays, Focus and summary settings for scheduled silences, and the desktop handoff for laptop-open lag. Change one thing at a time so you learn what actually fixed it, and you will get your work alerts back to real time without deleting a single app. The ping is supposed to reach you when it is sent. With the right layer cleared, it finally will.