Moderation - Troubleshooting

A moderator cannot see a command

Discord hides moderation commands from members without the matching permission (Timeout Members, Kick Members, Ban Members, Manage Messages; Timeout Members for /antiraid). Give the moderator's role that permission, or change the command's visibility under Server Settings > Integrations. The permission is still checked when the command runs. The full list is on the Overview.

"You cannot target a member with an equal or higher role."

Your highest role must be above the member's. Only the server owner can act on anyone (except themselves), and nobody can act on the owner.

"My highest role is not above this member's highest role."

Drag the bot's role above the member's highest role in Server Settings > Roles. The same applies to the mute role, roles restored on rejoin and anything anti-raid kicks.

The mass commands or /clean are refused although I have the permission

/massban, /massunban, /massmute and /clean need the bot's Staff level as well as the Discord permission. Add your role to Staff Roles under Permission Roles on the dashboard's Settings page, or use the single-target commands. Members with Administrator or Manage Server always count as Staff.

"This command is disabled." / "This module is disabled."

The command is switched off on the Commands tab, or the whole module is off (the switch at the top of the Moderation panel).

Cases are not posted to the log channel

Set a Case Log Channel on the Settings tab.
Give the bot View Channel and Send Messages there.
Mass actions never post per-user cases; their batch goes to Mod Logs.

/proof image or /proof file fails

"Failed to upload image - is the log channel set?" means there is no case log channel, or the bot cannot create or open the Proof thread there. Give it Create Public Threads and Send Messages in Threads in that channel. /proof url only accepts links starting with http:// or https://.

The member got no DM

DM user on action is off, or the action sends no DM (/mute, /note, the "un" commands and the mass commands never do).
The member has DMs from server members turned off, or shares no server with the bot any more. A refused DM is posted to Mod Logs as DM Failed when a channel logs that type.

The ban DM has no appeal link

The link appears only when the Forms module is enabled and has an enabled appeal form, and only for /ban and /forceban. Check both in the Forms panel, and make sure the Ban DM template contains {appeal_url}.

A timeout longer than 28 days ended early

Long timeouts are renewed by the bot. If the bot lost the Timeout Members permission, or its role is now below the member's, it cannot renew one; it posts a bot alert and retries with increasing delays. Fix the permission and the next renewal goes through.

A role was not taken off during a timeout, or not given back

The role is at or above the bot's highest role, or an integration manages it. The bot skips it and posts a bot alert once; move the bot's role above it. A held role in that state when the timeout ends stays owed, and comes back once the bot's role is above it.
The member left and rejoined: held roles come back only with Restore roles when a member rejoins on, and staff roles never do on their own.
The bot lost Manage Roles. It posts a bot alert; roles still to give back are retried with increasing delays once the timeout ends.
The module is switched off in the server: nothing is taken off then, not even when you add a role to the list (roles already held still come back).
A timeout that runs out is noticed within about two minutes, so the roles come back shortly after the end, not to the second.
Someone gave the role back by hand during the timeout: the bot takes roles off only when a timeout starts or changes, or when the list changes, so it stays until then.

A threshold did not fire

The infraction system is off (it is off by default); see Infractions.
Thresholds fire when an action crosses them. A member who was already above the threshold before the action does not trigger it again until decay brings them below it.
Actions by the bot itself, AutoMod cases with 0 points, and mass actions add no points.
The member outranks the moderator whose action crossed the threshold; staff get a bot alert instead.

Spam is detected but nothing happens

Anti-Spam only detects and logs. Add an automation rule on Any spam detected (or a specific spam trigger) with the actions you want; see Anti-Spam. If only some members are affected, check your scope overrides.

Anti-raid did not lock channels or change verification

The level still changes when Discord refuses an action; the refusal is posted to the level's notify channel. Lock Channels needs Manage Channels and Manage Roles, Verification Level and Block Invites need Manage Server, and Restrict Joins needs Kick Members. /antiraid status and /antiraid level answer "Anti-raid is disabled for this server." until you switch on Anti-Raid Protection.

Something else

The Logs tab shows every recorded staff action for Moderation. Problems the bot runs into on its own (a timed ban it cannot lift, a threshold it skipped) are raised as bot alerts: they appear in the server's staff logs and in Mod Logs when a channel logs the Bot Alert type.