Troubleshooting and FAQ
The usual reasons why something does not work, and short answers to common questions.
Start with $debug in the channel where something fails. It shows which permissions the bot is missing on the server and in that channel, the plan of the server, your permission level and, inside a ticket, its number, panel and state.
#The bot does not answer
- Check that the bot is online. The member list shows it, and the footer of this website shows the status of the service.
- Run
$debug. If the bot cannot write in the channel, it cannot answer there either. - Check the blacklist roles. Members with such a role are ignored.
- Check Command configs. The command may be off, or limited to other channels or roles.
- Mention the bot. It answers with the prefix of your server, in case somebody changed it.
#Missing permissions
Most errors come from a missing permission, often after a role change or in a private category. Give the bot's role the permissions listed in Getting started, and make sure categories and the panel channel do not deny them. Overwrites on a category beat server-wide role permissions.
#Everybody can see the tickets
@everyoneis a support role. Remove it.- The permissions of the group Everyone allow View channel. Set it to deny.
#A category is full
Discord allows 50 channels per category. Add overflow categories, or move closed tickets to a closed category.
#The server has 500 channels
Discord allows 500 channels per server, including categories and voice channels. Delete old tickets, use a trigger rule that deletes closed tickets after a few days, or switch busy panels to thread style.
#The channel name does not change
Discord lets a bot rename a channel twice per ten minutes. The bot skips renames beyond that instead of waiting. $rename tells you when you hit the limit.
#DMs do not arrive
Transcripts by DM and automatic DMs only arrive if the member allows direct messages from server members. Discord does not tell the bot why a DM failed, so the bot cannot retry it.
#The bot ignores prefix commands or custom commands
The bot needs the Message Content intent to read messages. On the hosted service it is on. If you host the bot yourself, turn on Server Members and Message Content under Bot · Privileged Gateway Intents in the Discord developer portal. Slash commands work without them.
#Buttons say "This interaction failed"
The bot was offline or restarting when the button was pressed. Press again after a moment. If it keeps failing, the panel behind the button may have been deleted: send the panel again.
#Questions
Can members see the dashboard? No. Only members with Manage Server, a dashboard role or the owner can open it.
I cannot see my server in the dashboard. You need Manage Server on it. If you got the permission just now, sign out and in again so Discord sends the new server list.
Can I import settings from another ticket bot? No. Panels are quick to set up, and backup keys copy settings between your own servers.
Does the bot work in several languages at once? One language per server, English or German. Messages you write yourself can be in any language.
What happens to tickets when I remove the bot? Channels stay in Discord as they are. Settings stay stored, so adding the bot again brings them back.