Match the symptom first
| What you see | Likely cause | Where to look |
|---|---|---|
| Every bot is slow or failing | Discord incident | discordstatus.com |
| Bot shows as offline | Its host or process is down | The bot's support server or status page |
| No commands when you type / | Command permissions | Server Settings, Integrations |
| An error instead of a reply | Bot missed the 3 second reply window | Wait, then try again; tell the developer |
| Command runs, nothing happens | Missing channel permissions | Channel settings, Permissions |
| Cannot give or remove a role | Role order | Server Settings, Roles |
| Ignores normal messages | No Message Content intent | Developer side only |
| Bot vanished from the server | Kicked or removed | Server Settings, Audit Log |
1. Check whether Discord is having issues
Before touching any settings, open discordstatus.com. It shows the state of the API and the other systems bots depend on, and lists current incidents. If the API is degraded, every bot slows down or fails at the same time and there is nothing to fix on your side. This is also the first place to look for general Discord technical issues like messages not sending or media not loading.
2. Check whether the bot is online
Find the bot in the member list. A bot is a program running on someone’s computer or a hosting service, connected to Discord’s Gateway. If that program crashes, runs out of credit or loses its connection, the bot stops answering. You cannot fix this from your server. Check the bot’s support server or website for an outage notice. If you run the bot yourself, look at its logs and restart it.
3. Make its slash commands visible
Members only see commands they are allowed to run. Three settings decide that:
- Use Application Commands. This permission controls whether a role can run slash and context menu commands at all. Find it in Server Settings, Roles.
- Integrations. Server Settings, Integrations, then the bot, lets you allow or deny each of its commands per role, member and channel. A deny here hides the command.
- Channel overrides. A channel can override what a role is allowed to do there.
Members with Administrator can use every command, so test with a normal account. If the developer just changed a global command, it can take a while to refresh for users, so fully restart Discord before you give up.
4. Commands that fail with an error
When you run a command, Discord sends it to the bot and gives it 3 seconds to send a first reply. A bot doing slow work is supposed to defer and answer later. If it is offline, overloaded or crashed, nothing comes back, Discord marks the interaction as failed and you see an error where the reply should be. Try once more after a minute. If it keeps happening, report it to the bot’s developer.
5. Fix permissions and role order
A command that runs but does nothing usually means the bot lacks a permission in that channel, such as Send Messages or Embed Links. Discord applies permissions from the server level down to the channel, and a channel deny wins over a server allow for that channel.
Role bots have one more rule. A bot can only edit roles that sit below its own highest role, and can only grant permissions it has itself. If an auto-role or verification bot “stopped working” after you made a new role, drag the bot’s role above it.
6. Bots that ignore normal messages
Bots that react to typed text, like old !command bots, need Discord’s Message Content intent. Without it the bot receives empty text, except in DMs with it, in messages that mention it and in its own messages. Only the developer can enable it, so if a prefix command died, check whether the bot moved to slash commands.
7. The bot is gone
If the bot disappeared from the member list, open Server Settings, Audit Log. It shows who kicked or removed it. Audit log entries are kept for 45 days. Re-invite the bot with its own invite link and redo its role position. If someone with permissions removed bots and deleted channels at the same time, treat it as a nuke and read what you can restore after channels are deleted.
Short checklist
- discordstatus.com is green.
- The bot shows as online.
- Its role is above the roles it manages.
- Use Application Commands is on for the role you tested with.
- No deny for the bot in Server Settings, Integrations, or in the channel.
- You tested with a normal account, not an admin.
For how these pieces fit together, see how Discord bots work.
A bot you do not have to host
Much of this list is about bots someone else keeps online. With VaultCord you get your own branded bot that runs online 24/7 on VaultCord’s side: 1 on Free, 3 on Premium and unlimited on Plus. It handles verification, backups and member restore, and support answers at help.vaultcord.com. The homepage shows how the restore works. Create your bot on the Free plan.