ReactionBot AI Troubleshooting

Confirm that ReactionBot is online and able to respond to standard slash commands in the server.

Make sure ReactionBot AI has been activated for the server and that the account connected to the activation still has valid AI access.

If standard ReactionBot commands also fail, review the Bot Not Responding troubleshooting page before testing AI again.

ReactionBot AI must be activated in the server before AI requests can be processed.

Run the /activateai command inside the server where you want to use ReactionBot AI.

Use the Discord account connected to the AI purchase or request balance when activating access.

Make sure you are signed into the same Discord account that was used when ReactionBot AI access was purchased.

If the purchase was completed using a different Discord account, ReactionBot may not be able to match the activation to your current account.

Confirm that the purchase completed successfully and that the AI access has not already been assigned elsewhere.

Your AI plan may support only a limited number of active server assignments.

Activating AI on a new server may require moving the existing assignment from another server.

Run /activateai in the intended server and follow any response explaining the current activation or transfer status.

ReactionBot AI cannot process new instructions when the available request balance has been exhausted.

Additional requests may become available when a recurring allowance renews or when another request pack is added.

Standard ReactionBot slash commands will continue to work according to the server's Free or Premium access.

A request can be interpreted correctly but still fail during permission, feature, or safety validation.

Read the full response for information about missing permissions, Premium requirements, role hierarchy, unavailable AI requests, or unsupported actions.

Try the equivalent slash command to determine whether the issue affects AI specifically or the underlying ReactionBot feature.

ReactionBot may be unable to act when the message does not identify the required emoji, member, channel, duration, limit, or scope.

Instead of saying “block it,” say “Block the fire emoji in this channel.”

Instead of saying “restrict them,” say “Restrict @User from reacting in this channel for two hours.”

Clearly state whether the action should apply to the current channel or across the entire server.

Use wording such as “in this channel,” “in #general,” “server-wide,” or “across the entire server.”

Review ReactionBot's confirmation before assuming the rule was applied to the intended scope.

Try including the actual emoji instead of describing it by name.

Common names such as “fire emoji” may work for standard emojis, but custom Discord emojis are more reliable when inserted directly into the request.

Avoid uncommon nicknames or descriptions that could refer to several different emojis.

Make sure ReactionBot can view and use the custom emoji within the relevant server context.

Insert the actual custom emoji into the message so ReactionBot can identify it accurately.

If the emoji belongs to another server or is unavailable to ReactionBot, the request may not be completed.

Mention the member directly using their Discord mention whenever possible.

Display names and usernames may be shared by multiple members or may not uniquely identify the intended person.

A request such as “restrict him” will fail when ReactionBot cannot determine which member you mean.

The person submitting the AI request must have the permissions required by the equivalent ReactionBot action.

ReactionBot AI cannot grant access to moderation tools that the user would not normally be allowed to use.

Ask a server administrator to review the user's Discord permissions and ReactionBot access.

ReactionBot must have permission to view the affected channel and perform the requested action.

Depending on the feature, permissions such as Manage Messages or Manage Roles may be required.

Check both the ReactionBot server role and any channel-specific permission overrides.

Actions involving another member may fail when that member's highest role is above the ReactionBot role.

Move the ReactionBot role above the roles it needs to manage while keeping its permissions limited to those genuinely required.

The requesting moderator must also have sufficient authority over the targeted member.

ReactionBot AI access does not automatically unlock Premium-only ReactionBot features.

Server-wide Reaction Control actions still require Premium when the equivalent slash command or dashboard setting requires Premium.

Use a supported channel-based action instead, or activate Premium on the server before retrying the server-wide request.

ReactionBot validates every action in a multi-action request separately.

One action may succeed while another fails because of missing information, permissions, role hierarchy, feature access, or Premium requirements.

Read the complete response and resend only the failed action with any missing details corrected.

Review the original message for unclear wording, missing scope, or details that could have more than one meaning.

Correct the configuration using a clearer AI request, the equivalent slash command, or the ReactionBot dashboard.

For major changes, use direct wording and confirm each result before submitting additional actions.

ReactionBot AI currently supports only features that have been specifically connected to the AI system.

A valid ReactionBot command or dashboard feature may still be unavailable through natural language.

Use the Supported Actions page to confirm availability, then use the standard command or dashboard for unsupported features.

Long messages containing many unrelated actions, users, emojis, channels, conditions, and time periods may be difficult to interpret accurately.

Split the request into smaller groups of related actions and include all required details in each message.

Use the dashboard when a large configuration change requires exact control over many settings.

ReactionBot AI may occasionally be unavailable because of a temporary ReactionBot, Discord, or AI service interruption.

Retry the request after confirming that ReactionBot is online and responding to normal commands.

Use the equivalent slash command when immediate access to the underlying feature is required.

This usually indicates an issue with AI activation, request availability, account access, or the AI processing service rather than the underlying ReactionBot feature.

Confirm the server's AI activation and remaining request access, then retry with a simple supported prompt.

For example, test with: “Block the fire emoji in this channel.”

Confirm that ReactionBot reported the action as successfully completed and that the rule was applied to the correct channel or server scope.

Check ReactionBot's permissions in the affected channel and review any channel-specific overrides.

Use the dashboard or equivalent list and configuration commands to verify the saved rule.

Record the exact prompt you submitted, the response ReactionBot returned, the server and channel scope, and whether the equivalent slash command works.

Also check your AI activation, request availability, Premium status, user permissions, bot permissions, and ReactionBot role position.

Providing these details makes it easier to identify whether the issue is caused by AI interpretation, account access, permissions, or the underlying feature.

Return to the ReactionBot AI Overview or Example Prompts page to review supported features and test a clear, simple request.