# Fix a flow or connection

Work through missing chat replies, blocked flows, silent alerts, Spotify problems and trouble signing in.

Updated 21 October 2026

## 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. In **Settings**, 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, a step that [reads a value before it’s set](https://bloopbot.com/docs/data-wires) 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.
- While you’re building your first overlay, Pebble watches for the overlay opening in your streaming app and says what it can see: nothing open yet, or something open that isn’t this overlay. See [Learn Bloopbot with Pebble’s tutorials](https://bloopbot.com/docs/tutorials#first-run).
- For an overlay, copy its current URL from Overlays. For a local HTML widget, check the file path on the streaming computer and its complete connection URL.
- For a custom overlay, choose it under **Overlays → Custom overlays** and press **Refresh status**. Its connected-source count should increase while the OBS scene is visible. Grant and subscribe to **stage.alert** and the matching `alert_design:name` record before testing an alert with **Test published output…** → **Play it on stream** on an alert layer.
- A label needs content; an alert layer stays blank until an alert plays on it. Use the relevant sample or test control.
- If a key or read token changed, replace the affected URLs in OBS. For the now-playing display that means the widget’s own URL: the old `/overlay/<token>/nowplaying` address still works but is no longer the way to set one up, and [put now-playing on stream](https://bloopbot.com/docs/now-playing-in-obs) covers the swap and the card that rotates or revokes the old token.

## 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 a custom overlay, [check its saved file path and access](https://bloopbot.com/docs/custom-widgets#duplicates). 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. Check the song variables on **Variables** — `song_max_queue` and `song_per_viewer` can turn a request down before it is searched for — and the blocked tracks, artists or viewers, which **Block or unblock** in your request flows holds. Then 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](https://bloopbot.com/docs/song-requests).
- **“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 reconnecting.** 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.

## I can’t sign in with Twitch

If you added a backup sign-in email, choose **Can’t use Twitch? Sign in with email instead** on the sign-in page and we’ll email you a link that opens your dashboard. Only an address you confirmed under **Account** can sign you in. If you haven’t added one yet, do it the next time you can sign in: [Keep a backup way to sign in](https://bloopbot.com/docs/backup-sign-in-email) walks through it.

## Sign in with a different Twitch account

1. In the dashboard, choose **Sign out** at the bottom of the sidebar.
2. Choose **Sign in with Twitch**. Twitch shows its authorisation page so you can check which account you’re using.
3. Use Twitch’s option to change accounts, sign in with the account you want, then approve access. For example, switch from your bot account to the account that owns your streaming channel.

You return to Bloopbot signed in as the account you chose. Signing out of Bloopbot does not sign you out of Twitch or disconnect your channel. If Twitch still uses the wrong account, sign out on Twitch itself and try again, or open Bloopbot in a private browser window.

## 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, private flow URLs, invite links and credentials before sharing.

## Still stuck? Ask in the Bloopbot Discord

Bloopbot has its own Discord server, where you can ask a person. Join it at [discord.gg/CANzH5SVpN](https://discord.gg/CANzH5SVpN). The first time, it asks what brings you there and shows the server rules to accept.

Channel owners also see a Discord card on **Overview** (**Join the Bloopbot Discord**, or **Unlock Free+ with Discord** on Free) until their linked Discord account is in the server. Choose **Join the Discord** there, or **Already a member? Link your Discord** if you are already in. If you signed up through a sign-up link that came with its own Discord invitation, that invitation appears in the card's place with its own button: it also gives you that link's role, and the cross button (**Dismiss the Discord invite**) hides it for your channel. You can always use **Bloopbot Discord** in the **Help** menu.

1. Open **#help** and search for your problem; someone may have asked already.
2. Start a post with a title that says what’s wrong, such as “!hello doesn’t reply”, and pick a tag.
3. Add the [problem report](https://bloopbot.com/docs/troubleshooting#report) from the section above, with any screenshots cropped.
4. When it’s fixed, tag the post **Solved**.

If something is broken rather than confusing, post in **#bugs** instead. Nobody from Bloopbot will message you first asking for your password.

This is Bloopbot’s server, not your own. To post in your Discord when you go live, see [Announce your stream in Discord](https://bloopbot.com/docs/discord-go-live).