SnowstormBot

Appearance

Troubleshooting ​

Quick fixes for the most common issues. If something here does not solve it, check the server status on the Servers page, since many problems trace back to permissions or a paused server.

The bot is offline or not responding ​

  • Confirm the bot is still in the server (check the Servers page; it should be under Bot installed).
  • Check the server's status chip. If it says Suspended or shows a logs-channel warning, the bot pauses its features there. See server status.
  • If it says Paused, you paused the bot on that server; click the resume button on the server card. If it says Disabled by SnowstormBot, our team temporarily disabled it, contact support. See pausing the bot on a server.
  • If a red banner at the top of every dashboard page says SnowstormBot is temporarily disabled, the bot has been paused everywhere for maintenance. Nothing is lost (your settings, commands, and data stay intact, and member and message activity is still recorded), and normal functionality resumes automatically once the banner clears. Scheduled actions that came due during the pause are not re-fired; scheduling just continues from whatever is next due.

The bot says it "isn't set up on this server yet" ​

The bot was added to the server without going through the website (for example with the "Add App" button on its Discord profile), or the server changed owner. It stays in the server but ignores commands and events until the server owner sets it up. The owner opens the Servers page and clicks Set up bot on that server. See Added the bot another way?

A command does not show up ​

  • Discord can take up to an hour to register command changes. Give it time.
  • Make sure the feature's feature is on. /rank and /leaderboard need XP & levels; /warn, /note, /warnings, and the action commands (/timeout, /kick, /ban, /nick, /role) need Moderation records.
  • For built-in toggles (/serverinfo, /userinfo), check the Default commands tab on the Commands page.

"Logs channel missing" or "Needs Manage Channels" ​

The bot keeps a #snowstormbot-logs channel and needs Manage Channels to do it. Grant that permission (or use Update permissions on the Servers page), then click the repair icon on the server's card. See the logs channel.

"Can't post in logs channel" ​

A #snowstormbot-logs channel exists, but its permissions stop the bot from seeing it or posting in it, and the bot was not allowed to fix that itself. Open that channel's settings, go to Permissions, and allow SnowstormBot to View Channel and Send Messages. The server recovers on its own once the bot can post. (If the bot can already see the channel and only posting is blocked, giving the bot Manage Roles also works, because then it can fix that itself.)

A role reward or role action does nothing ​

Discord only lets the bot manage roles below its own highest role. In Server Settings → Roles, drag SnowstormBot's role above any roles it should grant or remove (level rewards, the activity role, roles used in automations, and roles assigned with /role add).

A moderation action command fails ​

  • "You don't have permission...": you need one of the action commands roles, set in the Moderation records settings. Until roles are nominated, only the server owner can use them.
  • "...their highest role is the same as or above yours" or "...that role is the same as or above your own highest role": moderators can only act on members and roles below their own highest role, just like Discord's own tools. Ask someone higher up (or the server owner) to do it. See Moderators can only act on people below them.
  • "I couldn't check the server's role order right now...": the bot was not sure about the role order (usually just after a restart), so it stopped to be safe. Wait a moment and try again.
  • "Discord refused this action...": the bot is missing the Discord permission for that action, or its role sits below the target member's highest role. See permissions the bot needs and move the bot's role up if needed.
  • /ban or /unban always refused: servers invited before the ban commands shipped are missing Ban Members. Use Update permissions on the Servers page to re-grant the current permission set.

XP is not being awarded ​

  • Is the XP & levels feature on? It is off by default.
  • Is the channel or the member's role on the excluded list?
  • Remember the cooldown: a member earns at most once per cooldown window.
  • The member may have run /xp optout.

A feed is not posting ​

  • Is the subscription Enabled? Disabled feeds do not poll or receive pushes.
  • For RSS or GitHub feeds, check the poll interval; new items appear at the next poll, not instantly.
  • For YouTube, Twitch, and Kick, posts are pushed when the event happens. A go-live or upload that already passed will not re-fire; use Re-post the latest item if you need to repost it. New YouTube posts are usually instant, but can occasionally be delayed by up to about 30 minutes. This should be rare.
  • If the row shows a failure count, the source URL may be wrong or unreachable. Edit it and use Test feed to check (for Twitch and Kick this confirms the channel resolves).
  • Make sure the bot can post in the target channel.

Suggestions ​

  • I can't see the Accept / Deny buttons (or clicking them is rejected): only members with the Manage Server permission or the configured manager role can review suggestions. Set a manager role on the Suggestions page, or use a member who has Manage Server.
  • The bot didn't post my suggestion: make sure a suggestions channel is set on the Suggestions page, and that the bot has View Channel, Send Messages, and Embed Links in that channel.

A temporary voice channel was not created ​

  • Joining the hub does nothing / no channel is created: the bot needs Manage Channels and Move Members, plus View Channel and Connect on the category the channels are created under. Grant those, then rejoin the lobby.
  • I can't pick the category or lobby I want: the bot must be able to see the channel for it to appear. The lobby must be a voice channel and the category must be an actual category, not a text or voice channel.

My @role didn't ping in an embed or announcement ​

  • In the embed builder, select the role in the mention control (and switch on @everyone / @here if you need them). For /announce, pass the role to the role option. A role typed into the text alone never pings.
  • The bot also needs permission to mention roles (and Mention @everyone for @everyone / @here) in the target channel.

An embed was rejected or "too long" ​

Discord limits embed sizes. Keep within: title 256 characters, description 4096, each field name 256 and value 1024, footer 2048, author name 256, at most 25 fields, and 6000 characters total across the whole embed. Trim the part the dashboard flags and try again.

A scheduled message or job did not run ​

  • The server must be active (not suspended or deactivated).
  • The relevant feature must be on.
  • The schedule must be Enabled.
  • Check the time zone; the time shown is in the schedule's zone.

I can't invite the bot ​

  • Only the server owner can invite it.
  • You may be at your server cap (remove the bot from another server first).
  • The server may have too many members for your plan.
  • The server may have been suspended by a SnowstormBot administrator.

See Inviting the bot.

I can't sign in ​

  • Allow cookies for snowstormbot.net.
  • Sign out and back in after changing your Discord email or username.

Still stuck? ​

Open the server's audit log to see exactly what happened and when. If you believe something is broken, reach out through the support contact on the dashboard.