A Discord role cannot be assigned or removed
Diagnose a failed Clan Labs role bind or member update without changing unrelated Discord roles.
Last updatedSymptom
/update or Apps → Update User reports Auto Roles: Failed, lists Failed Roles, or leaves an expected role unchanged.
Most likely causes
- The Clan Labs bot lacks Manage Roles.
- The destination role is at or above the bot’s highest role.
- A saved bind points to a deleted or replaced Discord role.
- The user selected the wrong linked Roblox account or no longer matches the bind.
- Auto roles are disabled for the community.
Diagnostic checks
- Read the separate Auto Roles, Roles Added, Roles Removed, and Failed Roles fields.
- Check the member’s selected Roblox account, group membership, and current rank.
- Open the applicable rank or group bind and confirm the current Discord role.
- Confirm the bot has Manage Roles.
- Compare the destination role with the bot role in Discord’s role list.
Resolution
Restore Manage Roles, move the bot role above the role it manages, or update the bind to a current assignable role. Enable automatic roles if they are intentionally configured. Then run /update once for a test member and verify that only configured roles change.
When to retry
Retry after saving the permission, role-order, account, or bind correction. If Discord itself is delaying role updates, wait a few minutes and inspect the member before trying once more.
Contact support
Contact Clan Labs support when the role is current, below the bot, allowed by Discord, and still appears under Failed Roles.
Include this information
Include server ID, affected user ID, Discord role ID, Roblox user ID and rank, bind type, exact /update result, timestamp, and role-order screenshot. Do not include private tokens.