A Discord role cannot be assigned or removed
Fix failed role updates by checking binds, account selection, and Discord permissions.
Last updatedUse this guide when /update or Apps → Update User reports Auto Roles: Failed, lists Failed Roles, or leaves a role unchanged.
Fix it
Read Auto Roles, Roles Added, Roles Removed, and Failed Roles separately, then check the failed role:
| Check | Action |
|---|---|
| Auto roles are disabled | Enable them if your community uses automatic roles. |
| Wrong account or eligibility | Confirm the member's selected Roblox account, group membership, and rank match the bind. |
| Deleted or replaced role | Update the bind to a current assignable Discord role. |
| Missing Manage Roles | Restore the bot's permission. |
| Role is at or above the bot | Correct the hierarchy below. |
Correct the role hierarchy
Open Server Settings → Roles. Find the bot's highest role and each failed role. Move the bot above only the roles it must manage, then save. Roles at the same effective position are not manageable.
Keep sensitive administrator roles protected. If a role must stay above the bot, remove it from Clan Labs binds. Higher protected member roles can also block updates; the bot cannot change the server owner's nickname.
Check the result
After saving the correction, run /update for one test member. Confirm that only configured roles change and inspect any failed roles before updating more members. If Discord is delaying updates, wait a few minutes and inspect the member before retrying.
Still failing?
Contact support if the role is current, below the bot, and allowed by Discord but still fails. Include server and target-user IDs, bot and failed-role IDs, Roblox account and rank, bind type, exact result, timestamp, and a redacted role-order screenshot. Do not send tokens.