Bot not responding
Fix a Guild Pro bot that will not run a command, post in a channel or hand out a role.
Use this page when a slash command gives an error, a post does not appear in Discord, or a button on a bot message does nothing useful. Find the message you saw below.
Check the Bot page first
Open your guild on the website and go to the Bot page at /g/(your guild)/bot. Three things there tell you most of what you need:
- A card with your server name and disconnected means the bot is no longer in that Discord. An admin can click Add the bot again.
- A Needs attention card lists each channel the bot cannot post in and which permissions are missing.
- Recent activity lists what the bot did and what failed, with the reason.
A command replies that the Discord is not connected
Message: “This Discord is not connected yet. Add the bot at https://guildpro.io/dashboard.” or “This Discord is not connected to a guild yet.”
Cause: The bot is in the server, but the server has not been linked to a guild on the website.
Fix: Someone with the Manage Server permission in that Discord signs in on the website, opens /dashboard and adds the bot from there. See Install the bot.
A command says only officers can do that
Message: “Only officers can post a raid. An admin can add you on the members page” or “Only officers can post a roster call.”
Cause: Who may use these commands is decided by your role in the guild on the website, not by your Discord permissions. You need to be an officer or admin of the guild in Guild Pro.
Fix: Ask a guild admin to make you an officer on the guild’s members page. See Ranks and admins.
/setup tells you to go to the website
Message: “Setup lives on the website now.”
Cause: The /setup command has been retired. Channels, teams and who may post are now set on the website.
Fix: Follow the link in the reply. See Channel routes.
A post never appears in the channel
Messages:
- “The bot cannot see that channel. Give it access in Discord, or pick a different channel on the Bot page.”
- “The bot can see that channel but cannot post in it. It needs Send Messages, Embed Links and Attach Files.”
- “That channel no longer exists. Pick a new one on the Bot page.”
Cause: A channel permission in Discord blocks the bot, or the channel was deleted.
Fix: In Discord, give the bot’s role access to the channel with Send Messages, Embed Links and Attach Files. Or pick a different channel on the Bot page. Nothing is posted to a channel the bot cannot write in. See Permissions.
A role button does not give the role
Message: “Discord refused: the bot needs the Manage Roles permission, and its own role must sit ABOVE the roles it hands out. An admin can drag it up under Server Settings → Roles.”
Cause: Discord only lets a bot hand out roles that sit below its own role.
Fix: In Discord, open Server Settings, then Roles. Drag the bot’s role above every role it should hand out, and make sure it has Manage Roles.
Other role picker replies:
- “That role picker is gone. An officer removed it.” The message is left over from a picker that was deleted.
- “That role is not part of this picker any more.” The role was removed from the picker after the message was posted.
See Reaction roles.
A signup button says the raid is gone or closed
| Message | Cause |
|---|---|
| “That raid is gone.” | The raid was deleted on the website |
| “Signups are closed for this raid.” | An officer closed signups |
| “That roster call is gone. An officer can post a new one with /rostercall.” | The roster call was removed |
| “This roster call is closed.” | An officer closed it |
Ask an officer to reopen it or post a new one.
/recap says there is nothing imported
Message: “No raids imported yet. Paste an addon export at https://guildpro.io/import - or try /recap kind:dungeon.” or “No dungeon runs imported yet.”
Cause: The guild has no uploaded runs of that kind. The bot can only report on data that has reached the website.
Fix: See Data not showing up.
/rostercall says there is no WoW Forever guild
Message: “This Discord has no WoW Forever guild yet. An admin can add one on the website”.
Fix: See Add Forever to your guild.
The command was used in a direct message
Message: “Guild Pro only works inside a server.” or “Role pickers only work inside a server.”
Fix: Use the command in a channel of your guild’s Discord server.
Adding the bot failed
After you try to add the bot, /dashboard may show one of these:
| Message | Fix |
|---|---|
| “You need Manage Server in that Discord to add the bot.” | Ask someone with Manage Server to add it, or get the permission |
| “Install cancelled. Nothing changed.” | Start again and approve the Discord screen |
| “That install link had expired. Try it again.” | Start again from the dashboard and finish within 15 minutes |
| “That install did not match the server you picked. Try again.” | Pick the same server on the Discord screen that you picked on the dashboard |
| “Discord approved it, but the bot is not in that server yet. Try again.” | Add it again |
| “Sign in first, then add the bot.” | Sign in on the website, then retry |
“Something broke”
Message: “Something broke:” followed by a technical reason.
Cause: An unexpected error on the bot’s side.
Fix: Try the command once more. If it happens again, report it with the full text of the message. See Get help.
Related
Still stuck? Ask in the Discord.