ReactionBot Documentation
Reaction Control Not Working
Troubleshoot common issues that may prevent Reaction Control from moderating reactions in your Discord server.
If Reaction Control is not behaving as expected, the issue is usually related to permissions, channel configuration, or rule setup. The steps below cover the most common causes.
Run /diagnose First
The fastest way to identify most configuration issues is by running the /diagnose command.
The diagnostic report checks ReactionBot's permissions and can quickly identify common setup problems.
Verify Bot Permissions
ReactionBot requires View Channels, Read Message History, and Manage Messages to moderate reactions.
If any of these permissions are missing, reaction moderation may not function correctly.
Check Channel Permissions
Even if ReactionBot has the correct server permissions, individual channel overrides may prevent moderation.
Review the affected channel to ensure the required permissions have not been denied.
Confirm Your Rules
Verify that the appropriate Block, Allow Only, Limit Reaction, or Restrict User rules have been created.
If no matching rule exists, ReactionBot will allow the reaction as normal.
Review Global and Channel Rules
If using Global Rules, confirm that the affected channel is not configured to Ignore Global.
If Ignore Global is enabled, only that channel's Channel Rules will be enforced.
Test with a New Reaction
Reaction Control evaluates reactions as they are added.
If a rule was created after a reaction already existed, remove the reaction and add it again to test the new configuration.
Private Channels
ReactionBot cannot moderate channels it cannot access.
Ensure the bot has permission to view and manage reactions within private channels.
Discord Service Issues
Occasionally Discord may experience temporary API outages or delays.
If permissions and configuration appear correct, wait a few minutes and test again.
Still Having Problems?
If Reaction Control still isn't working after completing these checks, verify your dashboard configuration and test in another channel.
If the issue continues, contact the ReactionBot support server with the results from /diagnose and a description of the problem.