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.

[Watch the walkthrough](https://kb.trackiq.com/kb-assets/kbvideo-slack-stopped-explainer-704478e8.mp4)

*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**](https://kb.trackiq.com/hc/knowledge-base/articles/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**

![Aria in Slack, in Settings](/kb-assets/shot-slack-nav-c3006d.png)

**Settings &rarr; Aria in Slack.**

![The connection card](/kb-assets/shot-slack-card-a99cfb.png)

The card is the source of truth. It carries a status badge in the top right &mdash; **NOT CONNECTED** when the link is gone &mdash; and shows which workspace it is attached to.

**Not connected** &mdash; reconnect from this screen with **Add to Slack**. It is one click and, per the card, **no admin install is required** &mdash; it works with any workspace you already belong to. See [**Connecting TrackIQ to Slack**](https://kb.trackiq.com/hc/knowledge-base/articles/chatting-with-aria-in-slack).

**Connected to the wrong workspace** &mdash; 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** &mdash; 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 &rarr; Manage apps**. If TrackIQ is not listed, it was removed. Re-adding is the same one-click **Add to Slack** flow &mdash; no admin install needed &mdash; 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** &mdash; 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 &mdash; 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 &rarr; 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**](https://kb.trackiq.com/hc/knowledge-base/articles/alert-history-and-priority).

**Scheduled summaries** should arrive on their schedule regardless. If a daily summary is missing, that is a real failure &mdash; 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 &mdash; 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** &mdash; 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** &mdash; 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**](https://kb.trackiq.com/hc/knowledge-base/articles/chatting-with-aria-in-slack).

## **How to tell which one you have**

| Symptom | Most likely cause |
|---|---|
| TrackIQ itself is empty | not Slack &mdash; **Amazon connection** |
| Worked, then stopped dead | **2** &mdash; app removed |
| Aria replies, notifications do not arrive | **3** &mdash; channel |
| Aria does not reply | **1/2** &mdash; connection or install |
| Alert History is also empty | **4** &mdash; nothing triggered |
| Messages are in the channel when you scroll | **5** &mdash; your Slack settings |
| Answers arrive but the numbers look wrong | **3a** &mdash; wrong brand pinned |

## **If none of that explains it**

Collect these before contacting support &mdash; 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**](https://kb.trackiq.com/hc/knowledge-base/articles/getting-help).

## **Related**

- [**Connecting TrackIQ to Slack**](https://kb.trackiq.com/hc/knowledge-base/articles/chatting-with-aria-in-slack) &mdash; the setup, and how to redo it.
- [**Chatting With Aria in Slack**](https://kb.trackiq.com/hc/knowledge-base/articles/chatting-with-aria-in-slack) &mdash; the direct-message test.
- [**Setting Up Smart Alerts and Real-Time Notifications**](https://kb.trackiq.com/hc/knowledge-base/articles/setting-up-smart-alerts-and-real-time-notifications) &mdash; what should be arriving.
- [**Get Your Daily Number in Slack Without Opening TrackIQ**](https://kb.trackiq.com/hc/knowledge-base/articles/daily-number-in-slack) &mdash; the scheduled-summary side.
