Skip to main content

Common issues

Infusion is not responding to commands

If Infusion isn’t responding to your commands, try these solutions: Check bot status
  1. Verify that Infusion is online in your server’s member list.
  2. Check if Infusion’s status shows as “Online” (green indicator).
Verify permissions
  1. Ensure Infusion has the “View Channels” permission in the channel you’re using.
  2. Check that Infusion has “Send Messages” and “Use Application Commands” permissions.
Check command syntax
  1. Make sure you’re using slash commands (start with /).
  2. Verify the command name is spelled correctly.
  3. Ensure all required parameters are provided.
Server issues
  1. Discord may be experiencing outages. Check Discord’s status page.
  2. Try using the command in a different channel.
  3. Wait a few minutes and try again.

Commands are showing errors

“Missing permissions” error This means either you or Infusion lacks the required permissions. Solution:
  1. Check if you have the necessary permissions for the command.
  2. Verify Infusion has the required permissions (e.g., “Kick Members” for /kick).
  3. Ensure Infusion’s role is positioned above the roles it needs to manage.
“Invalid user” or “User not found” error Solution:
  1. Make sure you’re mentioning the user correctly using @username.
  2. Verify the user is still in the server.
  3. Try using the user’s ID instead of mentioning them.
“Invalid duration” error Solution:
  1. Use proper duration format: 10s, 5m, 2h, 1d.
  2. Ensure the duration is within acceptable limits.

Moderation actions not working

Kicks or bans failing Solution:
  1. Verify Infusion has “Kick Members” or “Ban Members” permissions.
  2. Check that Infusion’s role is higher than the target user’s highest role.
  3. Ensure you’re not trying to moderate a server owner or administrator.
Timeouts not applying Solution:
  1. Confirm Infusion has “Timeout Members” permission.
  2. Verify the timeout duration is valid (maximum 28 days).
  3. Check that the user doesn’t have “Administrator” permission.
Messages not being deleted Solution:
  1. Ensure Infusion has “Manage Messages” permission.
  2. Verify Infusion can access the channel where messages should be deleted.
  3. Note that messages older than 14 days cannot be bulk deleted due to Discord limitations.

Auto-moderation not working

Spam or links not being filtered Solution:
  1. Verify auto-moderation is enabled: /config automod <setting> enabled.
  2. Check that Infusion has “Manage Messages” permission.
  3. Ensure the channel isn’t excluded from auto-moderation.
  4. Verify moderators aren’t exempt from auto-moderation rules.
False positives If auto-moderation is too aggressive: Solution:
  1. Adjust sensitivity settings in the configuration.
  2. Add trusted roles to the exemption list.
  3. Whitelist specific channels where rules should be more lenient.

Logging issues

Logs not appearing Solution:
  1. Verify the log channel is set: /config modlog #channel.
  2. Ensure Infusion has “Send Messages” and “Embed Links” permissions in the log channel.
  3. Check that logging is enabled for the specific event type.
Incomplete log information Solution:
  1. Grant Infusion “View Audit Log” permission for more detailed logs.
  2. Ensure Infusion has been in the server for the events you’re trying to log.

Welcome messages not sending

Solution:
  1. Verify welcome messages are enabled: /config welcome enable.
  2. Check that the welcome channel is set: /config welcome channel #channel.
  3. Ensure Infusion has “Send Messages” permission in the welcome channel.
  4. Verify the welcome message format is valid.

Role management issues

Cannot add or remove roles Solution:
  1. Verify Infusion has “Manage Roles” permission.
  2. Ensure Infusion’s role is positioned higher than the role you’re trying to manage.
  3. Check that the role isn’t managed by an integration (bot roles, booster roles).
Auto-roles not being assigned Solution:
  1. Verify auto-roles are configured: /config autorole list.
  2. Ensure Infusion has “Manage Roles” permission.
  3. Check that Infusion’s role is higher than the auto-role.
  4. Verify the role still exists in the server.

Performance issues

Slow response times

Solution:
  1. Check your internet connection.
  2. Verify Discord’s API status.
  3. Try the command again after a few moments.
  4. If the issue persists, contact support.

Commands timing out

Solution:
  1. Avoid using commands that affect large numbers of users simultaneously.
  2. Break large operations into smaller batches.
  3. Wait between consecutive commands.

Configuration issues

Settings not saving

Solution:
  1. Ensure you have “Manage Server” or “Administrator” permission.
  2. Verify the command completed successfully (check for confirmation message).
  3. Use /config view to verify the settings were applied.

Lost configuration

Solution:
  1. If you have a configuration backup, use /config import to restore it.
  2. Reconfigure settings manually using the configuration commands.
  3. Contact support if you need assistance recovering settings.

Getting help

If you’re still experiencing issues after trying these solutions:

Check the documentation

Review the relevant documentation pages:

Join the support server

Get help from the Infusion team and community:
/support
This command provides a link to join our support server.

Report a bug

If you’ve found a bug:
  1. Join the support server.
  2. Provide detailed information:
    • What you were trying to do
    • What happened instead
    • Any error messages
    • Steps to reproduce the issue
  3. Include screenshots if possible.

Feature requests

Have an idea for a new feature?
  1. Join the support server.
  2. Share your suggestion in the feedback channel.
  3. Explain the use case and how it would benefit users.

Discord limitations

Some issues are due to Discord’s API limitations:
  • Messages older than 14 days cannot be bulk deleted.
  • Maximum timeout duration is 28 days.
  • Bots cannot moderate server owners.
  • Bots cannot manage roles higher than their own highest role.
  • Some actions require specific permissions that cannot be bypassed.
Keep Infusion’s role near the top of your role hierarchy to avoid permission issues.