Docs / Help / The bot does not respond

The bot does not respond

In short

Find what you see in the list below. Most refusals come from a service that is switched off, a Command Access rule or a permission the bot is missing.

Start with the reply the bot gave you, if it gave one. The problems are listed from the most common to the least.

The bot says a service "is switched off"

Why: The service that owns the command is switched off on this server. Every service starts switched off.

Fix: If you have Manage Server, press the Switch on button under the bot's reply, then run the command again. You can also open the dashboard, pick the server and go to Services, then turn the service on with the switch on its card. A service that is off keeps its settings, so nothing is lost when you turn it back on.

What the bot says when a service is off
Who ran the command or pressed the button What you see
The server's owner or a member with Manage Server "The Tickets service is switched off in this server. Switch it on, then try again." Under it are a "Switch on Tickets" button and a link to the dashboard.
Everyone else "The Tickets service is switched off in this server. Someone with Manage Server can switch it on. Run /yourbot to see what is switched on here."
  • The reply uses the service's name from the dashboard: Sentinel Moderation, Scheduled Announcements, Tickets, Giveaways, Beacon Events, Group Finder, Voice Channels, Welcome or Analytics.
  • Only you see the reply.
  • The button switches the service on and changes nothing else in your server. The service's pages on the dashboard hold its setup and every setting.
  • The first time Sentinel Moderation is switched on it starts with its recommended protection. The bot's answer says what that is.
  • A button or a menu on a panel in your server gets the same reply while its service is off. That covers the panels of Tickets, Beacon Events, Giveaways, Group Finder, Voice Channels and Welcome.
  • A voice room's control panel in your direct messages gets a shorter reply: "The Voice Channels service is switched off." It has no button. Someone with Manage Server can switch the service on from the dashboard.
  • The Leave button on a giveaway can still take you out of the giveaway while Giveaways is off.

The bot says I cannot use this command

Why: A Command Access rule refused you. The reply says which rule did it.

Fix: Open the dashboard, then Services, the service and Commands. Change the rule the reply named: add the role, add the channel, clear the cooldown or turn the command back on.

Every reply from this check
  • "This command is disabled on this server."
  • "You are not allowed to use this command."
  • "One of your roles is blocked from using this command."
  • "This command can only be used in {mentions}", where {mentions} lists the allowed channels.
  • "This command cannot be used in this channel."
  • "You need one of these roles to use this command: {mentions}", where {mentions} lists the allowed roles.
  • "This command is on cooldown. Try again in {N}s.", where {N} is the seconds left.

Two other refusals come from the same check:

  • "Command access settings are temporarily unavailable. Please try again shortly." The rules could not be read at that moment, so the command is refused instead of allowed. Run it again.
  • Moderation commands only: "Your account is frozen on this server after a recovery code was used. An owner can unfreeze it on the Sentinel Owners and recovery page."
Owners, Administrators and blocked members
  • The server owner can always run every command, unless their account was frozen after a recovery code was used.
  • An Administrator skips the role, channel and cooldown rules unless admin bypass is off for that command.
  • A blocked member is refused even when they are an Administrator.

A moderation command says "No permission."

Why: Moderation commands such as /quarantine, /lockdown and /case also need you to be an Administrator or to hold a moderator role. Command Access alone is not enough.

Fix: Ask an owner or manager to add your role as a moderator role on the Settings page of Sentinel Moderation. See Sentinel settings.

The bot answers but cannot do the job, or says it is missing permissions

Why: The bot can only act where its role and the channel permissions let it. When something is missing, it says what it could not do.

Fix: Run the Setup check:

  • On the dashboard: open Bot Settings, go to the Status tab and click Run the check on the Setup check card.
  • In Discord: run /yourbot with the check option set to Check my setup.

It lists each missing permission, the channel or role it affects and what stops working. Most lines have a Fix it link.

Examples, and why a permission goes missing
  • A reply from Voice Channels: "The bot is missing permissions on this room. Ask an admin to check its role."
  • A channel hidden from the bot counts as a missing View Channel.
  • A role that sits above the bot's highest role cannot be given out.
  • The invite asks for every permission the services can need. So a gap usually means a permission or a channel's permissions were changed afterwards. See Add YourBot to a server.
If the Setup check itself is refused

Members with Manage Server or Administrator can run it, and so can an owner or a manager on the dashboard. Anyone else gets "Only server admins can run the setup check. Ask someone with Manage Server to run /yourbot check." Ask a member who has one of them, or the server's dashboard owner or a manager.

The bot is not in my server, or its status says "Not in {name} yet"

Why: The bot has not been added to this server, or it was removed. On the Status tab of the Bot Settings page, the line under the bot's name reads "Not in {name} yet", where {name} is your server.

Fix: Go to yourbot.gg/invite. Or sign in, open the server list and click Invite bot next to the server. You need Manage Server on that Discord server. For a custom bot, click + Invite to Server at the top of the Bot Settings page.

My custom bot is stopped or crashed

Why: A custom bot runs as its own program. The Status tab of the Bot Settings page shows a notice when it is stopped or has crashed.

Fix: Use the button in the notice:

  • Your bot is stopped. "It shows as offline and your services can't answer anyone until you start it." Click Start.
  • Your bot crashed. "It starts again on its own in a moment. If it keeps crashing, its logs on the Status tab show why." To start it at once, click Start now.

My custom bot is quarantined

Why: The Status tab of the Bot Settings page shows Your custom bot is quarantined. The bot stays off until the cause is fixed. The notice names one of three causes.

Fix: Find the notice's words in the table, then do what that line says.

The notice says What to do
"Discord rejected its token. Paste a fresh token to bring it back." Click Paste a fresh token and paste a new one. Only an owner on the dashboard can change the token.
"Its privileged intents are off. Turn on Server Members Intent and Message Content Intent in the Discord Developer Portal, then turn it back on." Turn them on in the Discord Developer Portal. Then click Turn my custom bot back on.
"It crashed again and again, so it stays off until you turn it back on." Read why in its logs and fix that. Then click Turn my custom bot back on.
While your custom bot is off
  • While a custom bot is quarantined and the shared YourBot is in your server, the page says "Your server runs on the shared YourBot until then."
  • An action that was waiting while the bot was offline can be dropped. The page then says "While your bot was offline, {count} actions for this server were not sent." Click Got it to dismiss the notice.
  • An action that waits too long is not sent late. For Welcome's greetings and DMs, switching raid mode on and the actions of marketplace plugins, too long is 5 minutes. For most other actions it is an hour.
  • The page can also say "The bot service isn't answering". Your bot may still be running, and the page checks again every few seconds.

My custom bot has no active subscription

Why: The server has no active custom-bot subscription. The page says so, and the bot cannot start until one is assigned.

Fix: Assign a subscription to the server. See Shared bot vs custom bot.

The bot is offline for everyone

Why: If the bot does not answer anywhere and none of the causes above fit, the problem may be on YourBot's side.

Fix: Open the public status page. It needs no sign-in.

Was this page helpful?
YourBot docs Reference tables are generated from the code that is running. Ask in Discord