Skip to content
🤬 Troubleshooting

Troubleshooting

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.

Quick Issue Identifier

ℹ️ 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.

Step 1: Check Bot Permissions

The bot MUST have these 3 permissions in your channel:

Required Permissions

  1. View Channel - Bot needs to see the channel exists
  2. Read Message History - Bot needs to read past messages for deletion
  3. Manage Messages - Bot needs this permission to actually delete messages

For certain features or channel types, additional permissions may be required. Refer to the Bot Permissions Documentation for more details.

All three permissions are mandatory. Missing even one will cause the bot to malfunction.

How to Check Permissions

  1. Right-click on your channel
  2. Select “Edit Channel”
  3. Go to “Permissions” tab
  4. Find “EazyAutodelete” in the roles/members list
  5. Verify all three permissions are enabled (green checkmark)

Granting Permissions

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.

Step 2: Verify Your Configuration

Configuration errors are the most common cause of unexpected behavior. Use this checklist to verify each aspect of your config:

Configuration Checklist

Run /setup and review each setting:

  • Mode - Is the correct mode selected for your use case?

    • Mode 0 = Disabled (no deletion)
    • Mode 1 = Delete each message after time
    • Mode 2 = Delete all messages at intervals
    • Mode 3 = Delete messages after message count
    • Mode 4 = Delete oldest messages when limit exceeded
    • Mode 5 = Delete all messages daily at

  • Filters - Are the filters configured correctly?

    • Review each active filter
    • Ensure filters match the messages you want to delete
    • Check if you’re using the right Filter Behavior (match ALL vs match ONE)

  • Filter Behavior - Match ALL or match ONE?

    • “Match ONE” = Delete if message matches any filter (OR logic)
    • “Match ALL” = Delete only if message matches all filters (AND logic)

  • Limit - Is the limit value appropriate?

    • Mode 1 & 2: Time duration (10 seconds to 7 days)
    • Mode 3: Message count (3 to 75)
    • Verify format for time: 30s, 5min, 2hrs, 1day

  • Load Old Messages - Is this set correctly?

    • “Yes” = Process historical messages (up to 2 weeks)
    • “No” = Only process new messages

  • Roles - Are role filters working as intended?

    • Target roles = Only delete from these roles
    • Ignore roles = Don’t delete from these roles
    • Verify the correct roles are selected

  • Time Boundaries - Check “delete messages after” setting

    • Is there an unintended message ID restricting deletion?
    • Set to 0 to disable time boundaries

Common Configuration Mistakes

  1. Wrong mode for the use case: Using Mode 2 when you need Mode 1
  2. Conflicting filters: Having opposite filters (e.g., “Contains Emoji” + “Match ALL” + “No Emoji”)
  3. Role misconfiguration: Accidentally ignoring everyone or targeting no one
  4. Incorrect limit format: Using wrong time format or out-of-range values
  5. 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.

What /debug Shows

  • 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

How to Use /debug

  1. Run /debug in the channel you’re troubleshooting
  2. Review all displayed information carefully
  3. Look for status messages like:
    • “Waiting to be loaded” - Old messages are still being fetched
    • “Permission error” - Bot is missing required permissions
    • “Queue Length” - Number of messages waiting to be processed

Advanced Troubleshooting

Bot Not Deleting Anything

Possible causes:

  1. Mode is set to 0 (disabled)
  2. Filters are too restrictive (no messages match)
  3. All users have ignore roles assigned
  4. Time boundary excludes all messages
  5. Waiting for 60-second activation delay
  6. Still loading old messages (check /debug)

Solution: Review configuration checklist above and verify filters aren’t too restrictive.

Bot Deleting Wrong Messages

Possible causes:

  1. Filter Behavior set incorrectly (ALL vs ONE)
  2. Wrong filters selected
  3. Role configuration targeting wrong users
  4. Multiple overlapping configs in the same channel

Solution: Use /setup to review filters and Filter Behavior setting. Consider testing in a test channel first.

Bot Deleting Too Slowly

Possible causes:

  1. Very active channel with many messages
  2. Still loading historical messages

Solution: Mode 2 may be better for high-traffic channels. Check /debug for loading status. Check with support if delays persist.

Bot Deleted Pinned Messages

Possible causes:

  1. Filter “Is pinned” is selected instead of “Is not pinned”
  2. Message was unpinned before deletion timer expired

Solution: Always use Filter “Is not pinned” to protect pinned messages.

Threads, Forums & Categories

A thread or forum post isn’t being cleaned

  1. Check that Include Threads is enabled on its parent channel (/setup in the channel, or /forum-setup for whole forums) — thread coverage is off by default and is a Premium feature.
  2. For posts in forums under a category config, note that post coverage is controlled by Include Threads on the category config — enable it via /category-setup.
  3. If the thread is a private thread: the bot must be invited into it or have the Manage Threads permission. Private threads that can’t be seen by the bot are invisible to it by Discord’s design — no bot can cover them.
  4. Newly unarchived threads resume automatically — give it a few minutes after unarchiving.
  5. If the post vanished from a forum entirely: forums only contain posts (threads) — check whether it was archived or deleted; both states affect where its own page appears, not the cleanup rules once it’s back.

A category config deletes in one channel but not another

  • Channels just created or moved into the category are adopted automatically — usually within moments. If one seems stuck, re-save the config in /category-setup (this re-runs the fan-out).
  • Check whether the channel is inside the expected category (long-press → Edit Channel → Category).

Post Rules aren’t archiving/deleting anything

  1. Open /forum-setup → Post Rules and confirm the rule shows 🟢 Active — “Disable” vs. “Enable” are easy to miss, and a rule without at least one trigger+action stays off.
  2. The bot must have Manage Threads for the rule to be enableable at all.
  3. Check the exclusions: pinned posts are skipped by default; author-role/owner/tag filters may be excluding more posts than you think.
  4. Archived posts from before the feature existed are discovered and caught up at enable time where permissions allow — see Post Rules.

“Include Threads” shows an error or a Premium message

  • Turning thread coverage on requires Premium during rollout; turning it off is always free.
  • If you got a plain error, your server may be missing Manage Threads — grant it and retry.

Still Need Help?

If you’ve tried all the above steps and still can’t resolve your issue:

Contact Support

Visit our Support Server for personalized assistance.

Before asking for help, please:

  1. Run /debug in the affected channel
  2. Take a screenshot of your config (use /setup)
  3. Note your Channel ID and Server ID (from /debug)
  4. Describe what you expected vs what actually happened
  5. Mention any error messages you’ve seen

Our support team and community members are ready to help you get EazyAutodelete working perfectly!

Helpful Resources

Last updated on
✨ Premium🙌 Voting for Eazyautodelete