A member reached the warning threshold but wasn’t sanctioned: why?
Automatic sanctions are decided on every /warn, by counting the member’s active warnings. If nothing happens, check these points.
| Cause | How to spot it | Fix |
|---|---|---|
| The module is off | /config warn view shows “OFF”. Warnings are still recorded, but no sanction follows. | Turn it on (Warnings page or /config warn set enabled:oui). |
| The threshold is 0 | In the embed, the line shows “disabled”. | Set a number greater than 0. |
| The active total is too low | /warnings shows white dots (revoked) or expiry has expired the older ones. | Check the expiry. |
| The bot can’t sanction this member | Their role is above or level with the bot’s. The sanction is then simply skipped, with no error message. | See the role hierarchy. |
Good to know
- Only the highest threshold reached applies: if the ban is at 5 and the mute at 3, the 5th warning triggers the ban, not the mute.
- The sanction is attempted on every new warning as long as the total is at or above the threshold.
- The Auto sanction field of the
/warnmessage shows what was applied.
Still stuck?
Contact support with the title of this article, the step where you are stuck and what you see on screen.
Contact support More articles: TroubleshootingLast checked: 13 November 2026.