Moderation Server only

/timeout

Timeout a member

Usage

Generated
/timeout <member> <reason> [duration]
OptionTipoObligatorioDescripción
member member The member to timeout
reason text Reason
duration text No Duration: 60s, 10m, 1h, 1d, 7d (empty = the server's default timeout, when one is set)

Who can run it

Generated
Discord defaultMembers with Timeout Members
Command Access presetModerator roles
Always allowedThe server owner and, by default, Administrators
Change itDashboard, Services, Sentinel, Commands

The Moderation preset limits it to the roles you mark as moderators. Server owners and Administrators can always run it. How Command Access works.

What the bot needs

Generated

Sentinel is granted these permissions by the invite link. A command that finds one missing replies privately with what it could not do and changes nothing.

Kick MembersBan MembersManage ServerView ChannelSend MessagesManage MessagesEmbed LinksManage NicknamesManage RolesTimeout Members

Comportamiento

Checked against the code 2026-09-21

Times a member out on Discord and opens a case. Discord shows the command only to members with Timeout Members unless the server changes that under Server Settings > Integrations. 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."). It refuses to act on the server owner, on bots, and on anyone whose highest role is at or above the moderator's own ("Cannot action that member.").

The duration takes s, m, h, d or w units, for example 10m or 1d; a bare number counts as seconds. A value that does not parse is refused with "Invalid duration. Use: 60s, 10m, 1h, 1d, 7d, 28d". The option can be left empty: the bot then uses the server's default timeout from Settings > Moderator commands. When no default is set, it answers "Give a duration like 10m, 1h or 1d. To leave it out, set a default timeout under Sentinel Settings > Moderator commands." Anything longer than 28 days is cut to 28 days, which is Discord's limit.

With "Confirm before destructive actions" on, the bot first asks "Time out @member for 1h? Reason: ..." with Confirm and Cancel buttons. Only the moderator who ran the command can answer ("Only the moderator who ran the command can answer this."), and the prompt expires after 30 seconds with "Cancelled: no answer within 30 seconds."

The timeout is applied on Discord before anything is recorded. If Discord refuses it, because the bot lacks the permission or the member's highest role is above the bot's, the moderator is told and no case is opened. On success the bot opens a timeout case, sends the member the timeout DM when "DM on timeout" is on (stock text "You have been timed out in {server} for {duration}: {reason}", with an appeal hint added), and posts a "Timeout" card with the duration to the moderation log channel. The reply is "@member timed out for 1h. Case #12".

Good to know

  • When escalating timeouts are on under Settings > Repeat offenders and moderator timeouts are included, earlier timeouts inside the window lengthen this one. The reply then adds "Escalated from 10m: 2 prior timeouts in the last 30 days."
  • The timeout ends on its own. /untimeout lifts it early.
  • With anonymous moderation on, the DM and the log card say "the moderation team" instead of naming the moderator.
  • While an anti-nuke panic lockdown is on, only the server owner and the anti-nuke exempt users and roles can run it.
YourBot docs Reference tables are generated from the code that is running. Ask in Discord Suggest a correction