- Documentation
- Getting started
Common problems
The ten situations that come up most, and their cause.
Bao does not respond to commands
- Check with
/pingfirst. If the command is missing from the list, Discord has not finished propagating them: this can take up to an hour after installation. - The command may be disabled for this server, or restricted to roles you are not part of. See Enabling and restricting commands.
- A command whose feature is not included in your plan does not appear.
A role is never granted
This is problem number one, and the cause is almost always the same: Bao's role sits below the role to be granted. Discord forbids a bot from touching a role higher than its own.
Go to Server Settings, Roles, and move the Bao role above every role it manages.
Two other possible causes: the role is managed by an integration (another bot's role, a Twitch role), or it carries dangerous permissions that Bao refuses to grant automatically.
My server does not appear in the dashboard
Both conditions must be met: you are an administrator there or hold Manage Server, and Bao is installed there. If you have just been given the permission, sign out and back in: Discord takes a moment to refresh the list.
A scheduled message did not go out
Open the delivery log: the exact reason is written there. The most frequent ones are a deleted channel, a lost write permission, or an @everyone without the Mention Everyone permission.
The ticket will not open
- The member may have reached their open ticket limit, or be subject to the cooldown between tickets.
- They may be on the blacklist, or hold a role barred from opening.
- You may have set opening hours, and we are outside them.
- The category is full (Discord caps it at 50 channels) and no overflow category is declared.
The published panel no longer matches my configuration
This should not happen: any change updates the message automatically. If the message was deleted manually in Discord, publish the panel again.
The AI agent does not answer
- Check that the agent is enabled on tickets or on the channels concerned.
- In a public channel it only answers on mention, unless watch mode is enabled.
- The member may have reached their hourly quota, or hold a blocked role.
- Your AI credit allowance may be exhausted: the rest of the bot keeps working normally.
- The staff may have paused the AI on this ticket.
The AI agent answers off-target
Look at the knowledge gaps: they tell you exactly what is missing. If the agent invents facts about your server, the information is either absent from its base or present twice and contradictory.
Levels are not going up
Check the anti-spam delay (60 seconds by default), the excluded channels and the excluded roles. For voice, check the minimum number of humans required in the channel.
I can no longer see my history
This is not data loss. The depth of readable history depends on your plan: beyond it, an entry stays visible with its date, without its content. Everything becomes readable again if you move back up a plan. See History and retention.