Connected, but nothing arrives

What the app calls it

The same state is worded differently on the two screens that show it, so you may have met either one:

• the card under Connections → Monetization carries a yellow badge reading NOT RECEIVING, and the card's main button changes to Reconnect;
• the service's own page, in the Connection Status row, says Connected, but no events are arriving.

Only DonationAlerts reports this. Streaming platforms have no such state, so a silent Twitch or Kick chat is a different story — see "Sign-in required".

What it means

The connection is open and DonationAlerts accepted the subscription, but the service is not sending anything down it.

The app does not conclude that from silence — a quiet hour is normal. It proves it. Every fifteen minutes it reads your donation history from DonationAlerts and compares it with what came in live; the label appears only when a donation turns up there that never arrived through the live connection.

That same check delivers what it found. The donation still reaches alerts, goals, statistics and everything else — up to a quarter of an hour late instead of instantly. So the label means "arriving late", not "lost".

The usual cause is a second sign-in. Someone signed in to the same DonationAlerts account somewhere else: another computer, a phone, another app. The older session stays formally alive and simply stops receiving. That "someone else" is often you — the other machine you stream from, or a settings snapshot restored on a new computer.

What fixes it

In the order we tested during a live stream, and the order is not the one you would expect:

So the button to press is Reconnect on the card — or Authorize via Browser, if the DonationAlerts page is already open in front of you. Both start the same browser sign-in the "DonationAlerts Settings" guide walks through. Restarting the app is the natural thing to try and it does not help, because the connection was never the problem.

Why the warning stays after a restart

The label survives restarting the app on purpose. The problem survives it too, and a warning that disappears when you close the window would be worse than none: you would keep streaming, thinking it fixed itself.

It clears on two things only, both of them proof rather than hope: a donation arriving through the live connection, or signing in to the account again.

If it says CONNECTED and events are still missing

Then it is a different problem, and the card is not lying — the subscription is up and the check has not caught it missing anything. Look at these instead:

• The module is switched off. Its card in Module Catalog → Built-in — or under Add-ons, if you installed it yourself — says either "Module is running" or "Module is off — background work is paused". Judge by that card or by the Connections list, not by the module's own settings page: that page reads the saved account rather than the live connection, so it can go on showing its green wording while the module is off.
• The event does not exist on that platform. Follows and subscriptions arrive from Twitch only. The "Alerts" guide lists which platforms send which event.
• Alerts are filtered. A minimum amount, or a platform left unticked in the widget, quietly skips everything below or beside it — also in the "Alerts" guide.

YouTube says connected and the chat never arrives

This one has a cause of its own, and the card cannot show it. Google lists its permissions one by one on the sign-in screen and lets you untick them. Untick the one that lets the app see your broadcasts, and everything still looks right: the sign-in completes, the account name appears, the connection goes green and stays green — but the app never learns that you are live, and a chat it cannot find is a chat it cannot read. Nothing arrives, and nothing says why.

Signing in again is what fixes it, provided every checkbox is ticked this time. Nothing else will: renewing the sign-in in the background keeps exactly the permissions that were granted the first time, so it can go on renewing forever without ever gaining the missing one.

From 0.9.2 the app checks what Google actually granted and refuses a sign-in that came back short, telling you on that page to tick them all. On an older version there is no warning to look for — go to Connections → Channels → YouTube, press Authorize via Browser, and watch the checkboxes. The step is walked through in the "YouTube Integration" guide.

If it never worked at all

Then this is not the article you need — see "Signing in to platforms". This page is about a connection that worked and went quiet.