A Honeypot catch shows “failure”: why wasn’t the sanction applied?
In Latest catches (or in the log channel), a line says “failure” followed by the reason. The trap recognized the account and deleted its message, but the sanction could not be applied.
The most common cause: the hierarchy
Discord only lets a bot ban, kick or time out members whose highest role is below its own. A hijacked account that holds a high role therefore escapes the sanction.
- In Discord, open Server Settings › Roles
- Drag OriusBot’s role higher Above the roles of the members you want to be able to sanction.
- Check the role’s permissions Depending on the chosen response: Ban Members (softban and ban), Kick Members (kick), Timeout Members (timeout).
Other cases
- The “Deleted + warned” or “Deleted” response does not sanction, so it cannot fail this way.
- The server owner can never be sanctioned by a bot.
A red alert not to ignore
A trap that fails silently gives a false sense of security. Recheck the table after every role change. For the general list of permissions, see Which permissions to give the bot for each protection?
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: ProtectionLast checked: 13 November 2026.