Times out many members in one command: the ones named in targets, everyone who joined in the last joined_within minutes or both. Discord shows the /mass commands only to members with Timeout Members by default. The bot checks Command Access rules, that the Moderation service is enabled ("Sentinel is not enabled for this server.") and that the moderator is an Administrator or holds a moderator role from the Settings page ("No permission."). The moderator must also have Timeout Members ("You need the Timeout Members permission to run /mass timeout."). While anti-nuke is on, only the server owner, a Sentinel extra owner or an anti-nuke exempt account or role can run it ("Anti-nuke is on, so only the server owner, a Sentinel extra owner or an anti-nuke exempt account or role can run /mass timeout. Mass actions run as this bot, and anti-nuke does not watch this bot."), because the bot does the work and anti-nuke never acts on the bot. If the server's Sentinel settings cannot be read, nothing runs ("I couldn't read this server's Sentinel settings, so nothing ran. Try again in a moment.").
The duration is required and comes from a fixed list: 10 minutes, 1 hour, 6 hours, 1 day, 7 days or 28 days. The targets option takes mentions or user IDs separated by spaces or commas. The joined_within option takes 1 to 1440 minutes. At least one of the two is needed: "Name members in targets or set joined_within. You can use both." The bot's role needs Timeout Members: "I can't run /mass timeout: my role is missing Timeout Members. Give my role that permission, then try again."
The bot leaves out the server owner, itself, the moderator running the command, anyone no longer in the server, other moderators (Administrators and holders of a moderator role), bots not named in targets, anyone it could not look up and anyone whose highest role is at or above the moderator's or the bot's own. The server owner is not limited by their own role position. Members named in targets come first, then recent joins from newest to oldest. Each command times out at most 100; the rest are skipped as over the limit.
The plan is always shown first, whatever "Confirm before destructive actions" says, and only the moderator sees it. It opens with "Time out 12 members for 1h?" and up to 10 names, then the reason ("Reason: none given" without one). A skipped line counts who was left out and why, for example "Skipped 3: the server owner, 2 moderators." Then "Confirm within 30 seconds, or it is cancelled." sits above Confirm and Cancel buttons. Only the moderator who ran the command can answer, and without an answer the prompt reads "Cancelled: no answer within 30 seconds." When no one is left, the reply is "No one to time out." with the skipped line, and nothing runs.
On Confirm the prompt changes to "Working on 12 members..." and the bot times out one member at a time, 0.25 seconds apart. Members get no DM. Each member timed out gets a timeout case with the duration. Its reason starts with "Mass timeout:" followed by the reason given, or is just "Mass timeout" without one. Discord's audit log shows the same text. The case numbers run in a row. A "Mass timeout" card goes to the moderation log channel with who acted, the done, failed and skipped counts, the duration, the case range, the reason and the members timed out. The result arrives as a new message, for example "Timed out 12 of 12 for 1h. Cases #40 to #51. 3 skipped." The prompt then reads "Confirmed." Confirm runs every check again first, the anti-nuke rule and a frozen account included, and if one now refuses, the prompt shows that refusal instead and nothing runs.
One failed timeout does not stop the rest. The result adds the failed count and why, for example "Some had left the server before I got to them." After 5 refusals in a row the bot stops, counts the rest as failed and says "I stopped after 5 refusals in a row. Check my role position and permissions, then run it again for the rest." No case is opened for anyone who was not timed out.
Good to know
- Escalating timeouts ("Repeat timeouts get longer" under Settings > Warnings) never lengthen a mass timeout: every member gets the chosen duration. The cases still count as earlier timeouts when a later timeout is escalated.
- The timeouts end on their own. /untimeout lifts one early.
- Only one mass action runs in a server at a time; another is refused with "Another mass action is running in this server. Try again when it finishes." After a confirmed run the same moderator waits 30 seconds before the next one ("Wait 12 seconds before running another mass action.").
- The joined_within option reads the server's member list and Sentinel's own join log, so accounts that joined and left again show up as skipped, not in the server.
- With anonymous moderation on, the log card says "the moderation team" instead of naming the moderator.
- If the cases cannot be saved, the result says "The cases could not be saved. The actions above still happened."
- While an anti-nuke panic lockdown is on, only the server owner, Sentinel's extra owners and the anti-nuke exempt users and roles can run it.