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 arrive from Twitch only; subscriptions and gifted subs come from Twitch and YouTube; channel point rewards from Twitch and Kick. 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.

Kick: redemptions never arrive at all

A Kick channel connected before the app learned to read channel points carries no rights to them. Kick refuses every request, so nothing arrives — and the card stays green, because the channel connection itself is fine. The app writes the reason to the log console once and then keeps quiet.

Press Re-authorize on the Kick page and sign in again: the new sign-in asks for the reward permissions along with the rest, and the module keeps running while you do it. There is no Disconnect on that page any more; the step is walked through in the "Kick Integration" guide.

Kick: the bot says nothing when the message has a link

Chat works, the bot answers plain messages, and everything carrying a link is missing: a chat timer with your other socials, a command that replies with a link, an answer from the AI agent. Nothing goes red, because nothing failed on our side.

Kick delivers a link from a bot only while that bot is a moderator of your channel. It refuses the rest quietly, so the bot looks like it simply skipped its turn.

Make the bot a moderator: type /mod followed by the bot account name in your own Kick chat. The "Kick Integration" guide prints the command with your bot's name already in it, and the "Stream: Chat" tile writes the same reason into the feed the moment Kick refuses, so you can copy the command from there as well.

The moderator rule is what we have seen refused live, and it is about the bot. If the refusal lands on your own account instead, /mod is no cure at all: look at your channel's chat settings on Kick, where links can be restricted for everyone.

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.

The green badge is what tells this case apart. From strAImer 0.25.0, when the broadcast is found but its chat does not start, the YouTube badge on Connections → Channels is not green but CONNECTING... or ERROR: that is a different problem, covered in the article "Sign-in required", section "YouTube shows CONNECTING... or ERROR during a stream".

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.

"Worker crashed" in the log console

An error line Worker crashed: followed by a reason means the background part of one module stopped with an error. The app restarts it by itself, with growing pauses of 1, 2, 4, 8, 16 and 30 seconds, and writes that down too: "Restarting module in 1000ms (attempt 1)". One such crash followed by quiet is a hiccup that has already healed.

If the module keeps falling within a minute of every start, after six restarts in a row the line changes to Module keeps crashing (attempt 7), retrying every 60000ms. Last error: and the reason. The app does not give up and keeps trying once a minute, but while it falls the module does nothing: its alerts, commands or donations are what goes missing.

1. Switch the module off and on again on its card in Module Catalog, on Built-in or Add-ons.
2. If that does not help, restart strAImer.
3. If it still repeats, write to support and attach the log: the text after "Last error:" is the cause. The guide "Help" says how.

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.