ReactionBot Documentation
Bot Not Responding
Troubleshoot common reasons why ReactionBot commands or features may not respond.
If ReactionBot appears online but does not respond to commands or moderation events, the issue is usually related to permissions, channel access, role hierarchy, or server configuration. Follow the checklist below to identify the problem.
1. Check That ReactionBot Is Online
Confirm that ReactionBot appears online in your server member list.
If the bot is offline, commands and moderation features cannot function until the service reconnects.
2. Verify Permissions
ReactionBot requires the appropriate Discord permissions for the feature being used.
Missing Manage Messages, Read Message History, or View Channels permissions are the most common causes of failed moderation.
3. Check Channel Permissions
Channel-specific permission overrides can prevent ReactionBot from working even if server permissions appear correct.
If a feature works in one channel but not another, review the affected channel's permission settings.
4. Verify Role Hierarchy
ReactionBot's role must be positioned above members it needs to moderate.
Discord will ignore moderation actions against members whose highest role is above the bot.
5. Run /diagnose
Run /diagnose inside the affected channel.
The command checks common permission and configuration issues and is the fastest way to identify missing requirements.
6. Dashboard Configuration
If using dashboard features, confirm the correct channel is selected and the rule is enabled.
Saving dashboard changes may take a few seconds to synchronize with the bot.
Still Having Problems?
Join the ReactionBot Support Server for assistance from the community or development team.
Include screenshots of your permissions, role hierarchy, and /diagnose results whenever possible.