Slack notifications stopping is usually one of three things: the connection, the subscription, or Slack itself. They fail differently and the fix is different in each case, so it is worth finding out which before changing anything.
Prefer to watch? Ninety seconds on three failures that look identical, and the one-minute test that splits them.
Start here: is anything else broken?
Open TrackIQ and look at your dashboard.
If TrackIQ has no data either, this is not a Slack problem. It is an Amazon connection problem, and Slack is correctly reporting nothing. See Fixing a Broken or Expired Amazon Connection.
If TrackIQ has data and Slack does not deliver it, continue below.
That one check separates a delivery failure from a data failure, and it takes ten seconds.
1. Check the connection is still live
Settings → Aria in Slack.
The card is the source of truth. It carries a status badge in the top right — NOT CONNECTED when the link is gone — and shows which workspace it is attached to.
Not connected — reconnect from this screen with Add to Slack. It is one click and, per the card, no admin install is required — it works with any workspace you already belong to. See Connecting TrackIQ to Slack.
Connected to the wrong workspace — usually because someone reconnected from a different Slack account. Messages are going somewhere, just not where you are looking.
2. The app was removed from the workspace
A Slack workspace admin can remove an app without anyone in TrackIQ being told, and this is the most common silent cause in larger teams.
Symptoms fit a very specific pattern:
It worked, then stopped abruptly — no gradual degradation.
TrackIQ still shows the connection as it was.
Nothing appears in Slack at all, not even errors.
Check in Slack: workspace Settings & administration → Manage apps. If TrackIQ is not listed, it was removed. Re-adding is the same one-click Add to Slack flow — no admin install needed — unless your workspace restricts app installation generally.
3. The channel changed underneath it
Notifications go to a specific channel, and channels are not permanent:
The channel was archived.
The channel was made private and the app was not re-invited.
The channel was renamed — usually fine, but worth confirming.
The app was never invited to the channel in the first place. A public channel still needs the app present. In Slack, type /invite @TrackIQ in the channel, then mention @TrackIQ to use it.
A private channel is the classic case. Everything looks correct on both sides and nothing arrives, because the app cannot see the channel.
3a. The channel is pinned to the wrong brand
A distinct failure that looks like working software.
Each channel keeps its own brand pin. That is the point of the feature — Brand A in #marketing, Brand B in #ops. Aria remembers which one a channel is using and does not ask again.
So a channel can answer perfectly and be answering about a different brand than you assume. Numbers that look wrong rather than absent are frequently this.
Type switch in the channel to re-pick the brand.
4. Nothing has actually triggered
Some notifications are event-driven, so no message can mean no event.
Alerts fire when their condition is met. A quiet week is a quiet channel. Check Alerts → History in TrackIQ: if there are no recent alerts there either, Slack is working and there has simply been nothing to say. See Alert History and Priority.
Scheduled summaries should arrive on their schedule regardless. If a daily summary is missing, that is a real failure — a missing alert may not be.
Distinguish "no messages" from "no messages that should have existed" before escalating.
5. Your own Slack settings
Two personal settings suppress messages that were delivered perfectly:
Do Not Disturb hides the notification, not the message. Scroll the channel — if the messages are there, delivery is fine.
Channel muted, or notification preferences set to mentions only. Same symptom, same check.
Look in the channel before assuming nothing arrived. This resolves a surprising share of reports.
6. Ask Aria something directly
If Aria is connected, message it in Slack and see whether it answers.
It answers — the connection is healthy, so the problem is subscription or channel routing, not the link. Note that replies in Slack are text-only; charts and tables are web-only, so a missing chart is not a fault.
It does not answer — the connection or the app installation is the problem. Back to steps 1 and 2.
This is the fastest single test available, and it separates the two halves of the problem cleanly. See Chatting With Aria in Slack.
How to tell which one you have
| Symptom | Most likely cause |
|---|---|
| TrackIQ itself is empty | not Slack — Amazon connection |
| Worked, then stopped dead | 2 — app removed |
| Aria replies, notifications do not arrive | 3 — channel |
| Aria does not reply | 1/2 — connection or install |
| Alert History is also empty | 4 — nothing triggered |
| Messages are in the channel when you scroll | 5 — your Slack settings |
| Answers arrive but the numbers look wrong | 3a — wrong brand pinned |
If none of that explains it
Collect these before contacting support — they are what will be asked for:
Which workspace and channel.
When it last worked, roughly.
Whether Aria replies to a direct message.
What TrackIQ's Aria in Slack screen shows now.
See Getting Help from the TrackIQ Team.
Related
- Connecting TrackIQ to Slack — the setup, and how to redo it.
- Chatting With Aria in Slack — the direct-message test.
- Setting Up Smart Alerts and Real-Time Notifications — what should be arriving.
- Get Your Daily Number in Slack Without Opening TrackIQ — the scheduled-summary side.