Fix a flow or connection

The bot does not reply to a command

1. Check the selected channel and that the flow is live rather than paused.
2. Read the trigger’s Command, Prefix and aliases. Use exactly that command in chat.
3. Save any pending edits. Check that the action is connected to the trigger through the intended conditions.
4. Review permission, cooldown and live-stream checks. A failed condition may be stopping the flow correctly.
5. Open Links and review Twitch and bot-account status. Follow a re-authorisation prompt if one is shown.

A flow needs attention or stops early

The Overview counts flows that need attention and marks them in its list. Open Flows → Needs attention and follow the reported requirement. Common causes include a missing Twitch permission, a disconnected integration, a missing variable or a graph that cannot run.

Open the flow’s Run log. Find the first failed or stopped node, inspect its inputs and check the outgoing path. Use Test fire after saving your fix. A dry run does not verify live Twitch permissions or actual OBS delivery.

OBS is blank or the test never arrives

• Keep the correct OBS scene and Browser Source visible. Hidden sources may be shut down.
• For a hosted widget, copy its current URL from Widgets. For a local HTML widget, check the file path on the streaming computer and its complete connection URL.
• Check the type of source in Alerts → Connected to OBS. A hosted label cannot receive a custom alert-card test.
• A label needs content; an alert box may be blank until an event. Use the relevant preview or sample.
• If a key or read token changed, replace the affected URLs in OBS.

A message or alert appears twice

Look for two enabled flows with the same command or event trigger, especially after installing a pack. Check OBS for duplicate sources. For older custom widgets, follow the setup page’s guidance about removing the sb= parameter. Pause one duplicate path at a time and test again.

A song request is accepted but does not play

Confirm Spotify is linked, Premium is available and playback is active on the intended device. Review queue limits and blocked tracks, artists or viewers. Check the Song requests flow group for disabled or duplicate commands.

Spotify will not link, or chat says it is not set up

• “Spotify isn’t set up for this channel.” The channel owner has not saved a Spotify app yet. Follow step 1 of the song requests guide.
• “Spotify rejected your Client ID or secret.” Re-copy both values from the Spotify dashboard, and check that the Redirect URI in your Spotify app matches the one on the Spotify card exactly.
• Spotify shows an error after you approve. Link with the same Spotify account that owns the app. A development-mode app only admits its owner and the few people the owner adds in the Spotify dashboard.
• Needs Reauth. Press Re-link Spotify on the card. If there is no button, save your Spotify app first.
• It worked and then stopped. Spotify stops an app when its owner’s Premium lapses; it resumes when Premium returns. “This channel’s Spotify app has hit its API quota” clears on its own after a short wait.
• The Link Spotify button sends you to sign in. Linking is only available to the signed-in channel owner. Editors cannot link, re-link or unlink Spotify.

Collect a useful problem report

Record the page, flow name, what you expected, what happened and the relevant error from the Run log. Include the time of a real event if useful. Crop screenshots to the problem area and remove widget URLs, webhook URLs, invite links and credentials before sharing.