Slack alerts not arriving: trace the route in minutes
Errors fire in AllStak but nothing lands in your Slack channel. The route has exactly three links — the connection, the rule, and the channel — and one of them is broken.
What this looks like
New errors, uptime failures, or security events appear in the AllStak dashboard, but the Slack channel your team watches stays quiet. Sometimes alerts used to arrive and stopped — typically after a Slack admin removed the app, the channel was archived, or someone deleted the notification rule.
Two things must both be true for an alert to land: the Slack integration is connected via OAuth, and a notification rule routes that event type to a selected Slack channel. Either one missing produces silence with no error on your side.
Common root causes
Connected, but no notification rule
The OAuth connection alone does not send anything. A notification rule must route the event type (new errors, uptime failures, security findings…) to Slack — no rule, no alert.
No channel selected on the rule
Each rule targets a channel chosen from the channel picker. A rule pointing at a deleted or archived channel delivers nowhere.
Workspace revoked the app
If a Slack admin removed the AllStak app or revoked its authorization, deliveries fail until the integration is reconnected through OAuth.
Bot not in a private channel
The bot can join public channels automatically, but private channels require a member to invite it — alerts routed to a private channel the bot is not in are not delivered.
Step-by-step diagnosis
Walk the route in delivery order: connection, rule, channel, then a live test.
- 1
Confirm Slack shows as connected
Open the Integrations page in the AllStak dashboard and check the Slack card's status. If it is not connected, run the OAuth flow again — connection is a couple of clicks with no tokens to copy.
- 2
Check a notification rule routes your event type
Review your notification rules and confirm one routes the event type you expect (e.g. new errors) to Slack. Rules are per event type and per channel — an uptime rule does not deliver error alerts.
- 3
Verify the target channel still exists
Open the rule's channel selection and re-pick the channel from the picker if it shows stale. Archived and deleted channels are the classic cause of alerts that "used to work".
- 4
Invite the bot to private channels
If the destination is a private channel, invite the AllStak bot from inside Slack (e.g. /invite). Auto-join covers public channels only.
- 5
Reconnect if the workspace revoked the app
Ask your Slack admin whether the AllStak app was removed or its authorization revoked. If so, reconnect from the Integrations page — the OAuth flow restores delivery without rebuilding your rules.
- 6
Trigger a matching event and watch the channel
Fire an event of the exact type your rule routes — e.g. a test error — and confirm the alert lands with its action buttons. Remember deduplication: a spike of identical errors arrives as one alert, not many.
Prevent it from recurring
- After connecting or changing rules, always fire one test event before relying on the route.
- Route alerts to a dedicated public channel rather than a private one when possible.
- Tell your Slack admins the AllStak app powers production alerting — so it is not removed casually.
- When archiving a channel, update or retarget the notification rules pointing at it first.
Still stuck?
If the connection, rule, and channel all check out and a test event still does not arrive, check the AllStak status page, then email [email protected] with your organization name, the rule's event type, and the channel — we can trace the delivery from our side.
Frequently asked questions
I connected Slack — why is nothing arriving?
Connecting is half the route. You also need a notification rule that routes your event type to a selected Slack channel. Create the rule, pick the channel, and trigger a matching event to confirm.
Why do I get one Slack alert for hundreds of identical errors?
That is deduplication working as designed — a spike of identical errors arrives as one actionable alert instead of a flood that buries the channel.
Can different events go to different channels?
Yes. Create multiple notification rules, each routing its own event types to its own channel — backend errors to one channel, uptime alerts to another.
Do alerts work in private Slack channels?
Yes, once a member invites the AllStak bot into the private channel. Public channels are joined automatically; private ones always need the invite.
Explore more
By framework
Compare
Alerts your team can act on
Connect Slack with OAuth, route the events that matter, and triage with Resolve, Snooze, and Assign buttons right in the channel. Start free.