Skip to content

Discord bot not working? Find the cause and fix it

Last updated on November 19, 2026 · VaultCord Support

When a bot stops working, the cause is almost always one of five things. Three of them you can fix in your server settings in a minute. The other two you can only wait out. This article goes through them in the order worth checking, so you do not spend twenty minutes on permissions during a Discord outage.

Discord's sideYour server's sideVaultCord's side
Gateway or API trouble. Every bot goes quiet at once.Permissions, channel overrides, role order, how the bot was added.Only if the bot is your VaultCord bot. Ask at help.vaultcord.com.

1. Check whether every bot is down, or just one

Open your member list and look at the other bots. If all of them are offline or silent, the problem is upstream. Discord publishes its status at discordstatus.com, split into components such as API, Gateway, Push Notifications, Search, Voice by region and Client. Bots receive events over the Gateway and answer through the API, so trouble on either one stops bots everywhere. Nothing in your server settings will fix it. Wait, and avoid re-inviting or kicking bots while it lasts.

If only one bot is affected, carry on below.

2. Is the bot online at all?

A bot with a grey status dot is not connected. Bots are programs that run on their developer’s servers, and when that host crashes or the developer’s token is reset, the bot drops offline for every server at once. Check the bot’s support server, website or status page. You cannot fix this from your side, and removing the bot will not help.

If the bot is not in your member list at all, it may have been added with only the applications.commands scope. Discord’s docs say that scope can be used on its own, which adds the app’s commands without a bot user. Bots that need to read messages, give roles or join voice must be added with the bot scope.

3. Check its permissions in that channel

A bot that is online but ignores one channel is nearly always blocked by a channel permission override. Go through this list:

  1. Right-click the channel, open Edit Channel, then Permissions.
  2. Check the bot’s role and the bot itself. It needs View Channel and Send Messages, plus Embed Links if it posts embeds.
  3. Check @everyone overrides too. A red X there applies to the bot unless its role is allowed explicitly.
  4. For voice, it needs Connect and Speak in that voice channel.

4. Check the role order

A bot can only give, remove or manage roles that sit below its own highest role. If a verification, auto-role or moderation bot “does nothing” when it should assign a role, open Server Settings, then Roles, and drag the bot’s role above the roles it hands out. It also needs the Manage Roles permission. This is the single most common reason a role bot looks broken.

5. Commands that time out or get ignored

What you seeLikely causeWhat to do
“The application did not respond”The bot did not answer the interaction within 3 secondsCheck Discord’s status, then tell the bot’s developer
Prefix commands like !help do nothingBot lacks the Message Content intentUse the bot’s slash commands, or @mention it
Slash commands are missingScope, permissions or install typeSee the slash commands article
Works for admins onlyCommand permissions limit who can use itServer Settings, Integrations, the bot, Command Permissions

Discord’s developer docs say an app must send its first response to a command within 3 seconds, or the interaction token is invalidated. Slow hosts and Discord API trouble both cause this, which is why step 1 comes first.

Message Content is a privileged intent. Without it, a bot still receives each message, but the text arrives empty, so a prefix never matches. Discord’s guidance to developers is to move to slash commands. As a server owner you cannot switch the intent on, but you can use the bot’s slash commands, or mention it, since bots can always read messages that mention them.

When to ask for help, and who to ask

  • One third-party bot is broken: its own support server or website. Discord support does not fix other people’s bots.
  • All bots and Discord itself are broken: wait for discordstatus.com to show recovery.
  • Your VaultCord bot: help.vaultcord.com with your server ID and a screenshot.

Questions people ask

Why is my Discord bot not working?

The most common causes, in order: Discord itself is having trouble, the bot’s own host is down, the bot lacks a permission in that channel, its role sits below the role it is trying to manage, or it relies on reading message text without the Message Content intent.

Why is my Discord bot not responding to commands?

For slash commands, Discord needs an answer from the bot within 3 seconds or it shows an error. For prefix commands like !help, a bot without the Message Content intent receives the message with an empty content field, so it never sees the prefix.

Why is my Discord bot not showing as online?

An offline bot means its program is not connected to Discord’s gateway. Either the bot’s host is down, or Discord’s gateway is having trouble. Check discordstatus.com first, then the bot’s own support server.

Why is a bot not showing up in my member list?

If the bot was added with only the applications.commands scope, there is no bot user in your server at all, only its commands. Re-add it with the bot scope selected if it needs to be a member.

Why is my bot not joining the voice channel?

Check that its role has Connect and Speak in that voice channel, and that the channel is not full. Music bots also depend on their own audio sources, which can break without any change on your side.

All articles · VaultCord questions: help.vaultcord.com