Skip to content
StreamerCatalyst Docs

Troubleshooting & FAQ

General

I signed in but the dashboard shows no modules

Make sure you signed in with the Twitch account that owns the channel you want to manage. StreamerCatalyst ties module configuration to the channel that authenticated.

If you are a moderator, you will see the dashboard in read-only mode until you switch into a channel via the Mod link. Your broadcaster needs to have connected their account first.

Modules are greyed out or locked

Greyed-out modules require a higher subscription tier. See Module access by tier and Tier comparison. You can upgrade under Settings → Billing.

My Twitch OAuth expired — how do I reconnect?

Go to streamercatalyst.com, sign out, then sign back in with Twitch. This refreshes all tokens. If you see “Channel tokens expired” errors in the bot API, that same re-login fixes them.

Chatters / Bot API

The bot API returns “No chatters found — is the stream live?”

The Chatters API fetches your live chatter list from Twitch. If the stream is offline or no one has chatted recently, Twitch returns an empty list. The bot command only works while you are live with viewers in chat.

The bot API returns “Invalid or missing apikey”

Double-check that you copied the full 64-character API key from Chatters → Settings → API key. If you recently regenerated it, update the key in every bot command that uses it.

My Nightbot / StreamElements command returns an error message instead of a name

The bot pastes the API’s plain-text response directly to chat, including error messages. The most common causes are:

  • Stream is offline.
  • API key was regenerated and the old key is still in the bot command.
  • The filter you set returned zero chatters (e.g. filter=sub with no subscribers in chat).

Test the URL directly in a browser while streaming to see the raw response.

Commands are not responding in chat

  1. Check that the bot is switched on (Chatters → Overview → Enable Chatters). That’s the bot kill switch, not a plan setting.
  2. Check that the bot identity account (the account that types commands) is still authorised and has not had its token revoked.
  3. Check that the command is enabled and not restricted to mods when a regular viewer is trying to use it.

Events

Reward rules are not firing

  1. Confirm rule firing is switched on (Events → Settings → Module).
  2. Check that you have an active event open. Rules only fire within an active event window. Open one from the Events dashboard.
  3. Check that the triggering Twitch EventSub subscriptions are active. In the dashboard, go to Events → EventSub and verify subscriptions are listed and enabled. If not, click Set up subscriptions.

A rule fired but no message appeared in chat

The Events module sends messages via the Twitch bot identity configured in the module settings. Make sure:

  • The bot identity is set and authorised.
  • The bot account is not banned or timed out in your channel.
  • For AI-generated messages, check that your daily AI token budget has not been exhausted.

Cumulative totals seem wrong after enabling cumulative mode

When you first enable cumulative mode on a bits or gifted-subs rule, a backfill job runs to populate historical totals from the existing transaction log. This can take a moment. Refresh the dashboard after a few seconds to see updated totals.

Widgets

My widget shows a blank screen

  1. Check that the browser-source URL is the full URL copied from the Widgets dashboard (it includes a token parameter).
  2. In your streaming software, make sure the browser source has the correct width and height to match the widget’s configured dimensions.
  3. Check that your stream minutes quota has not been reached for the month. See Tier comparison.

Widget is not updating in real time

The widget receives updates over WebSocket. Common causes of stale data:

  • The browser source was opened while offline and never reconnected. Reload the browser source in your streaming software.
  • A network firewall or VPN is blocking WebSocket connections to widgets.streamercatalyst.com.

Custom widget code throws errors

Open the browser source’s dev tools (in OBS: right-click → Interact → open dev tools) to see JavaScript errors. Custom widget runtime errors are also logged in Widgets → Runtime errors in the dashboard.

Modomation

Redemption automations are not firing

  1. Confirm Modomation is enabled.
  2. Check that the rule has an active EventSub subscription — click Subscribe on the rule card if the subscription status shows as inactive.
  3. Twitch EventSub subscriptions can become disabled if your broadcaster token expires. Re-authenticate via the dashboard to refresh the token, then re-subscribe the rule.

Auto-shoutout is shouting out the same person repeatedly

Check the cooldown setting in Modomation auto-shoutout config. If cooldown is set to 0 or null it fires on every message from that viewer. Set a positive cooldown (seconds) or use once per stream mode to prevent repeats.

Numbers

My analytics show 0 events even though the stream is live

Numbers collects events via Twitch EventSub. Make sure the EventSub subscriptions are active:

  1. Go to Numbers → EventSub in the dashboard.
  2. If subscriptions are missing, click Set up subscriptions to register them.
  3. Subscriptions can also lapse when the broadcaster’s Twitch token expires — re-login fixes this.

Old data disappeared

Data retention is capped by your subscription tier. Streams older than the retention window are pruned automatically. See Tier comparison for retention limits per tier. Upgrading to a higher tier preserves future data for longer but does not restore already-pruned records.

Still stuck?

If the above steps do not resolve your issue, submit feedback via the Feedback button in the dashboard. Include a description of what you expected to happen and what happened instead. Screenshots and browser console output help the team diagnose issues faster.