Slack Message Won't Send ("Couldn't send" / Red Exclamation)? Fix It

Your Slack message sits there with a red exclamation mark or a “Couldn’t send” / “Failed to send” notice.

Why: A failed send almost always means Slack briefly lost its live connection to the server — from a flaky network, an outage, a stale local cache, or security software cutting the link. The message is saved locally, so you can usually just retry once the connection is restored.

Fix 1: Retry the message and check your connection

1. Hover over the failed message and click Retry (or the red exclamation icon) to resend it.
2. If it fails again, check your internet: open another site, or toggle Wi-Fi off and on.
3. Try a different network (e.g. switch from office Wi-Fi to a phone hotspot). If it sends there, the original network is the problem.
4. Disable any VPN or proxy temporarily — a dropped VPN tunnel breaks Slack’s connection and blocks sends.

Fix 2: Check Slack’s status

1. Open status.slack.com.
2. If there’s an active Messaging or Connections incident, the issue is on Slack’s side. Your message is saved — it’ll send once service is restored.

Fix 3: Clear cache and restart (desktop)

A stale local cache can leave the app “connected” but unable to send:

1. Click Help in your top menu bar (or the ☰ menu on Windows) → Troubleshooting → Clear Cache and Restart.
2. After it reopens, retry the message.
3. Make sure your desktop app is up to date — outdated versions can break sending.

Fix 4: Antivirus, firewall, or proxy

Security software can block Slack’s WebSocket connection so messages never leave:

1. Temporarily disable your antivirus or ad-blocker and resend. If it works, add Slack to the software’s allowlist rather than leaving protection off.
2. On a work network, a proxy/firewall may be cutting the connection on port 443. Ask IT to allow the URLs at your my.slack.com/help/urls page and exempt wss-primary.slack.com, wss-backup.slack.com, and wss-mobile.slack.com.

FAQ

Will I lose the message if I close Slack? No — unsent messages are stored locally and reappear as drafts/failed sends when you reopen Slack. Retry them then.

Only one channel fails to send? That’s usually a connection blip rather than a channel problem — retry, and if it persists run Clear Cache and Restart (Fix 3).

It says sent but others don’t see it? Confirm at status.slack.com there’s no delivery incident, then have them refresh — a cache clear on their side (Fix 3) often syncs it.

Sources: Slack Help Center — Troubleshoot connection issues · Slack Help Center — Manage Slack connection issues