Troubleshooting
Fix common AutoMod problems.
| Problem | Likely cause | Fix |
|---|---|---|
| Messages are not checked | No AutoMod row exists, the filter is disabled, the author is a bot, or the message is in the suggestion channel. | Enable the filter in /dashboard/<guildId>/automod and test outside the suggestion channel with a normal member. |
| Spam does not trigger at exactly the limit | The code triggers when count is greater than antiSpamLimit, not equal. | For “5 in 5 seconds”, expect the 6th message in the window to trigger. |
| Allowed link is still blocked | The allowlist stores bare domains and compares host names after removing www.. | Add example.com, not a full URL such as https://example.com/path. |
| Caps messages are ignored | The message has fewer than 8 letters or uppercase percentage is below threshold. | Test with a longer all-caps sentence or lower capsThreshold. |
| Message is not deleted | Bot lacks Manage Messages or cannot access the channel. | Grant Manage Messages and ensure the bot can view and send in the channel. |
| Timeout, kick, or ban silently fails | Discord role hierarchy or missing permissions prevents the action. | Move the bot role above target roles and grant the matching moderation permission. |
| WARN DMs are missing | The member has DMs closed. | This is expected; AutoMod catches DM failures and continues. |
First rule wins
If a message is both a link and all caps, the link action may not run if spam triggered first. Tune spam limits if it is hiding later rules during testing.
