A silent Cloudbot can mean the bot is disconnected, or it can mean one command, timer or loyalty setting is not behaving as expected. Start by sorting the symptom: if every feature is quiet, check connection and permissions first; if only one feature fails, inspect that feature’s settings before restarting everything.
The checks differ by platform and by Cloudbot configuration. Streamlabs’ Cloudbot Common Problems & Solutions is the main reference for the documented steps below; treat them as diagnostic checks, not a guaranteed fix. If they do not resolve the problem, contact Streamlabs support rather than guessing at undocumented causes.
Identify the Cloudbot symptom
First establish the scope. Ask whether Cloudbot is absent or silent everywhere, whether a single command is failing, whether timers are quiet or appearing together, or whether loyalty points are missing. Also note which platform is in use and whether the stream is public. These distinctions matter: a YouTube public-stream condition, for example, will not explain a Twitch command’s cooldown.
| What you see | First area to check | A useful distinction |
|---|---|---|
| No commands or other bot activity | Connection and platform permissions | Does any simple command work? Is Cloudbot present where the platform shows a viewer list? |
| One command gets no reply | That command’s settings | Does a default command or unrestricted test command work? |
| Timers do not post | Timer toggle and conditions | Has the interval passed, and has enough recent chat occurred? |
| Several timers post together | Timer intervals | Parallel timers can coincide; they are not a queue. |
| Some viewers do not receive points | Loyalty rules and platform behaviour | Are they active chatters, and are the relevant payout amounts enabled? |
| Several unrelated features stop at once | Connection or a wider service issue | Check the connection sequence and current Streamlabs notices before changing each feature. |
Keep a short record of what you tested: platform, whether the stream was public, which test command worked, and the setting or time when the symptom occurred. That lets you avoid repeating a connection check when the evidence points to one timer, and gives support useful details if escalation is needed. Do not infer a service-wide outage from one failed command or an old incident report.
Check whether Cloudbot is connected
If everything is quiet, confirm Cloudbot is enabled for the relevant platform and that the bot account has the needed moderator permission. Check that the account name is the right one: if you configured a custom bot name, it is that account which needs the permission, not automatically the default Streamlabs name. Where the platform provides a viewer list, check whether the bot appears there. Then try a simple command so you know whether the failure is genuinely connection-wide.
Streamlabs’ platform instructions are not interchangeable. For Twitch, its troubleshooting guidance says to use /mod Streamlabs to grant moderator status; if the custom bot name is in use, mod that name instead. For YouTube, the guidance directs creators to add the Streamlabs bot channel through YouTube Studio community settings. Check the current YouTube Help instructions for managing moderators alongside Streamlabs’ setup guidance, because account interfaces and permission controls can change.
For YouTube, also confirm the live stream is public. Streamlabs says Cloudbot will not join a private stream. If you are using an unlisted or private broadcast, do not treat a missing bot as proof that a command setting is wrong; first check the visibility requirement in the current official instructions. You can see why this matters in a different streaming context in our guide to streaming a Hindi bhajan playlist as a YouTube Live loop, where stream setup and audience availability are part of the operating plan.
If permissions and visibility look correct but the bot is still unresponsive, Streamlabs documents a restart sequence: turn Cloudbot off, wait between 2 and 10 minutes, then turn it on again. The wait range is the one given in Streamlabs’ troubleshooting page, not a timing guarantee. If you recently changed your name, relog and re-enable the bot as directed there; then consider its documented unmod/remod and disconnect/reconnect steps for Streamlabs services. Change one thing at a time and retest, so you can tell which check affected the symptom.
Some setup checks apply only to particular configurations. Streamlabs’ guidance discusses an Alert Box in every scene in a collection, or launching an Alert Box widget in a browser and muting that browser if alerts are not wanted in every scene. It also says to avoid using the streamer’s personal Twitch username as the bot username and to refresh a browser source cache where relevant. These are not universal connection requirements. Use them only when you have a custom bot or a browser-source/Alert Box issue that matches the symptom.
If Cloudbot responds to a test command but not to a timer or payout, stop treating it as wholly disconnected. Move to that feature’s checks instead. This prevents a broad reset from obscuring a setting that is specific to one command or one platform.
Troubleshoot commands that do not respond
When one command fails, test a default command or create a simple .test command without permission settings. If that works, Cloudbot can respond and the problem is more likely within the original command’s configuration or trigger. If neither test works, return to the connection checks rather than editing a command that may not be receiving chat at all.
For the failing command, check the exact trigger text and make sure the command is enabled. Inspect its permission level: a command configured for moderators, for example, will not necessarily answer an ordinary viewer. Check any cooldown as well. A command can appear broken when it is simply still within its configured cooldown, or when the user is not permitted to invoke it.
A loyalty-point cost is another possible condition. If a command requires points, check that the viewer has enough to meet that cost; this is distinct from a command being disabled or Cloudbot being offline. Test using an account and conditions that can satisfy the configured requirement, rather than assuming that silence means the bot failed.
If the command uses a variable or parameter, check that the particular parameter is supported in that part of Cloudbot. Streamlabs notes that some parameters are restricted to specific Cloudbot sections. A variable copied from another feature may therefore not work in the place you put it. Use Streamlabs’ current command documentation or support guidance for the relevant section rather than trying undocumented syntax.
Avoid changing several commands at once. Record the trigger, permissions, cooldown and any point cost before adjusting one setting, then test again. If a default command works and your unrestricted test works but the configured command does not, that is useful evidence for a support request if the documented checks do not resolve it.
Check timers that do not trigger
A timer has more than one condition. Confirm that it is enabled, that its interval has elapsed, and that its line minimum is met. Streamlabs says Cloudbot counts chat lines from the previous five minutes toward the line minimum. A timer may therefore be switched on and still remain quiet when chat is too slow, even though its interval has passed.
On YouTube, check that the stream is public as well; Streamlabs applies the public-stream condition to Cloudbot joining. Do not assume a timer’s lack of activity has the same cause as a Twitch timer that is enabled but waiting for enough chat. In either case, compare the observed behaviour with the timer’s actual settings before changing the schedule.
Timers run in parallel, not in a queue. Streamlabs’ documentation explains that timers with intervals that coincide can trigger together. For example, its troubleshooting guidance uses 10-, 15- and 20-minute schedules as an illustration of intervals that meet at common multiples. If you want posts to be more staggered, it gives 5, 7 and 11 minutes as an example set with less frequent overlap. These values are examples from its guidance, not a universal best schedule; choose intervals that suit your audience and content.
This can explain two symptoms that look opposite: no timer post may point to an unmet interval or line minimum, while simultaneous posts may be expected behaviour from overlapping intervals. Do not disable a timer just because it appears beside another one at a shared time. If the schedule is crowded, adjust one interval and observe whether the timing becomes more useful.
For a channel that runs a recurring playlist, timer messages can also be part of the viewer’s orientation: a song title or a reminder may be more helpful than several notices at once. Our article on showing the current song title on a 24/7 YouTube music stream covers a related presentation problem, but it is not a substitute for checking Cloudbot’s interval and line-minimum rules.
Investigate missing loyalty payouts
Start with the loyalty feature’s own configuration. Confirm it is enabled, review the payout interval against the length of your stream, and check that live-user and active-user reward amounts are not set to zero. The interval determines how often points are awarded, so a viewer may not receive a payout immediately after entering chat. Streamlabs’ loyalty guide also explains that an active-user payout stacks with the live-user payout; consider the two settings separately when comparing what a viewer should have received.
Platform behaviour changes who is eligible. Streamlabs says YouTube does not provide a viewer list for this purpose, so only active users who type in chat receive the active-user points. A viewer who watches without typing may not receive that payout. This is not the same as an enabled loyalty system failing for every viewer; compare a chatting viewer’s result with a lurker’s before changing payout amounts.
For Twitch or Kick, do not import the YouTube explanation as a universal rule. Check the relevant platform’s current Cloudbot support instructions and the actual eligibility settings for your channel. Streamlabs’ documentation distinguishes platform behaviour, and the available information here does not establish that every platform tracks viewers in the same way.
If points still seem missing, note the payout interval, the live and active amounts, whether the viewer typed, and the platform. Avoid repeatedly changing values without recording them; otherwise it becomes difficult to tell whether the original symptom was a timing expectation, zero reward, or platform eligibility difference.
Check platform-specific issues
Use the platform named in the symptom, not the one most familiar to you. Twitch’s moderator command and YouTube Studio’s bot-channel permissions are different procedures. Likewise, YouTube’s public-stream requirement and its lack of a viewer list for loyalty payouts affect particular checks; they do not establish a common root cause for Twitch, YouTube and Kick.
| Platform or setup | Relevant documented check | Do not assume |
|---|---|---|
| Twitch | Confirm the configured bot account is modded; Streamlabs documents /mod Streamlabs for the standard name. |
A custom bot name has the same permission as the standard account. |
| YouTube | Confirm the bot channel is added in YouTube Studio community settings and the stream is public. | A private stream will behave like a public one, or a lurker receives active-user points. |
| Kick | Check the current Streamlabs platform guidance and the permissions for the connected account. | Twitch or YouTube instructions apply unchanged. |
| Custom bot/browser-source setup | Check the custom account’s moderator status and relevant Alert Box/browser-source configuration. | Every Cloudbot user needs the same scene or cache steps. |
When permissions seem right but Cloudbot remains missing, use Streamlabs’ documented restart and reconnection sequence for the platform and account involved. If you manage a continuous YouTube channel through other tools as well, keep the symptoms separate: a broadcast stopping is not the same failure as Cloudbot going silent. Our guide to restarting a YouTube livestream after a failure addresses stream recovery, not Cloudbot permissions.
When to contact Streamlabs support
Contact Streamlabs when you have completed the relevant documented checks and the symptom persists, or when you cannot tell whether the account is connected correctly. Streamlabs directs users to its Discord community or a support ticket. Include the platform, bot name, whether it is enabled and modded, whether a default command works, and the exact feature that fails. For a timer, include its interval and line minimum; for loyalty, include payout settings and whether the affected viewer typed in chat.
If several features fail together despite valid settings, treat a wider connection or service issue as possible, not certain. Run the connection checks and consult current Streamlabs support notices. Streamlabs documented a past incident affecting timers, default commands and custom commands and marked it resolved. A resolved historical notice does not show that the same issue is happening now, so use current notices or support rather than diagnosing a present outage from it.
A 24/7 YouTube channel may have a separate operational concern: keeping the video broadcast running while your own computer is off. StreamNeo turns an uploaded video into a YouTube live stream, so you do not have to keep a local computer running for that broadcast. It does not change Cloudbot’s platform permissions or configuration, and it is YouTube-only; keep bot troubleshooting with Streamlabs and assess broadcast continuity as a separate requirement.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Why is Streamlabs Cloudbot not responding at all?
Check that it is enabled, has moderator permissions under the correct account name, and appears in the platform’s viewer list where one is available. Test a simple command; for YouTube, also confirm that the live stream is public. If those checks pass, follow Streamlabs’ documented off-and-on restart and reconnection sequence, then contact support if the bot remains silent.
Why do Cloudbot timers post together?
Timers run in parallel, so intervals that share common multiples can coincide rather than queue one after another. Review the intervals and stagger them if that suits the channel; also confirm the timer is enabled and its interval and recent-chat line minimum are both satisfied.
Why are YouTube viewers not receiving loyalty points?
Streamlabs says YouTube has no viewer list for this loyalty behaviour, so a viewer who only watches without typing is not eligible for the active-user payout. Check that loyalty is enabled, the interval is appropriate, and both live-user and active-user rewards are nonzero; consult current Streamlabs guidance if active chatters still do not receive points.
What should I send Streamlabs support?
Describe the platform, whether Cloudbot is enabled and modded, which test commands worked, and whether one feature or several are affected. Include the relevant command, timer or payout settings and the checks you already tried. That gives support a clearer starting point than reporting only that the bot is broken.