Experiencing issues with EazyAutodelete? This guide covers the most common problems and their solutions. Most issues can be resolved by checking permissions, verifying your config settings, or using the /debug command.
ℹ️ Common Issue: Configs Keep Resetting to Mode 0?
If your configs automatically change back to Mode 0 (disabled), this means the bot has detected an error in your channel configuration. This is a safety feature to prevent incorrect operation. Follow all the steps below to identify and fix the issue.
The bot MUST have these 3 permissions in your channel:
- View Channel - Bot needs to see the channel exists
- Read Message History - Bot needs to read past messages for deletion
- Manage Messages - Bot needs this permission to actually delete messages
All three permissions are mandatory. Missing even one will cause the bot to malfunction.
- Right-click on your channel
- Select "Edit Channel"
- Go to "Permissions" tab
- Find "EazyAutodelete" in the roles/members list
- Verify all three permissions are enabled (green checkmark)
If permissions are missing:
- Grant them to the @EazyAutodelete role server-wide, OR
- Add a permission override specifically for EazyAutodelete in your channel
Still having issues? Verify that no other role or permission override is denying these permissions to the bot.
Configuration errors are the most common cause of unexpected behavior. Use this checklist to verify each aspect of your config:
Run /setup and review each setting:
- Wrong mode for the use case: Using Mode 2 when you need Mode 1
- Conflicting filters: Having opposite filters (e.g., "Contains Emoji" + "Match ALL" + "No Emoji")
- Role misconfiguration: Accidentally ignoring everyone or targeting no one
- Incorrect limit format: Using wrong time format or out-of-range values
- Forgetting the 60-second delay: Changes take 1 minute to apply
Need help understanding a setting? Check our detailed documentation:
¶ Step 3: Use the /debug Command
The /debug command is your best troubleshooting tool. It provides crucial information about your channel's status and configuration.
- Channel ID and Server ID - Useful when contacting support
- Active configs - All configs in the channel and their current state
- Bot status - What the bot is currently doing
- Loading status - Whether old messages are being loaded
- Error messages - Any detected problems with permissions or configuration
- Processing queue - How many messages are waiting to be processed
- Run
/debug in the channel you're troubleshooting
- Review all displayed information carefully
- Look for status messages like:
- "Waiting to be loaded" - Old messages are still being fetched
- "Permission error" - Bot is missing required permissions
- "Mode 0" - Config is disabled (check why)
- "Processing X messages" - Bot is actively working
- "Waiting to be loaded": Normal for Mode 3 or when loading old messages. Be patient.
- "Mode 0 - Disabled": Something went wrong. Check permissions and config.
- "No configs found": You haven't created a config yet. Use
/setup.
- "Permission denied": Missing one of the three required permissions.
Possible causes:
- Mode is set to 0 (disabled)
- Filters are too restrictive (no messages match)
- All users have ignore roles assigned
- Time boundary excludes all messages
- Waiting for 60-second activation delay
- Still loading old messages (check
/debug)
Solution: Review configuration checklist above and verify filters aren't too restrictive.
Possible causes:
- Filter Behavior set incorrectly (ALL vs ONE)
- Wrong filters selected
- Role configuration targeting wrong users
- Multiple overlapping configs in the same channel
Solution: Use /setup to review filters and Filter Behavior setting. Consider testing in a test channel first.
Possible causes:
- Discord API rate limits (normal behavior)
- High server load
- Multiple Mode 3 configs in one channel
- Very active channel with many messages
- Still loading historical messages
Solution: This is often normal behavior due to Discord's rate limits. Mode 1 is typically faster than Mode 2 or 3.
Possible causes:
- Filter "Is pinned" is selected instead of "Is not pinned"
- Message was unpinned before deletion timer expired
Solution: Always use Filter 8 "Is not pinned" to protect pinned messages.
If you've tried all the above steps and still can't resolve your issue:
Visit our Support Server for personalized assistance.
Before asking for help, please:
- Run
/debug in the affected channel
- Take a screenshot of your config (use
/setup)
- Note your Channel ID and Server ID (from
/debug)
- Describe what you expected vs what actually happened
- Mention any error messages you've seen
Our support team and community members are ready to help you get EazyAutodelete working perfectly!
- "Why is my config in Mode 0?" → Check permissions
- "Messages aren't being deleted" → Verify filters and limit settings
- "How do I protect pinned messages?" → Use Filter 8 "Is not pinned"
- "Can I delete messages older than 2 weeks?" → No, Discord API limitation
- "Why is there a 60-second delay?" → Prevents constant bot restarts during configuration
