A role is above the Clan Labs bot’s highest role

SymptomCopy link to Symptom

A role action fails even though the bot has Manage Roles, or Clan Labs identifies a role that is above the Clan Labs bot’s highest role.

Most likely causesCopy link to Most likely causes

• The managed role is physically above the bot role in Discord’s role list.
• The managed role and bot role are at the same effective position.
• A newly created or renamed role changed the hierarchy.
• The target is the Discord server owner or has a higher protected role.

Diagnostic checksCopy link to Diagnostic checks

1. Open Server Settings → Roles.
2. Find the highest role assigned to the Clan Labs bot.
3. Find each role named by the failed update.
4. Confirm every managed role is below the bot role.
5. Check whether the target is the server owner; bots cannot change the owner’s nickname and Discord protects some owner interactions.

ResolutionCopy link to Resolution

Drag the Clan Labs bot role above only the roles it needs to manage, then save. Do not give the bot a position above sensitive administrator roles unless its workflows genuinely require that. If the role should remain protected, remove it from Clan Labs binds instead.

When to retryCopy link to When to retry

Run /update on one test member after Discord saves the hierarchy. Inspect Roles Added, Roles Removed, and Failed Roles before updating more members.

Contact supportCopy link to Contact support

Contact Clan Labs support if the role is visibly below the bot and Discord’s audit or error response still rejects the action.

Include this informationCopy link to Include this information

Include server ID, target user ID, bot role ID, failed role ID, exact error, timestamp, and a redacted role-order screenshot. Never share a Discord token.