A member’s Discord roles or nickname do not update
Reconcile the selected Roblox account, Clan Labs binds, Discord roles, and nickname permissions.
Last updatedThe Clan Labs member profile, Discord roles, or nickname does not reflect the intended Roblox account or rank after verification or a change.
Fix it
- Confirm the profile’s Roblox user ID and current public group rank.
- Run
/updateor Apps → Update User once. - Read Auto Roles and Nickname separately.
- Inspect Roles Added, Roles Removed, and Failed Roles.
- Review active rank or group binds and the bot’s Discord permissions.
Select the intended linked Roblox account, correct the bind, enable the desired automatic behaviour, and fix the bot permission or hierarchy named by the result. Run one more update and verify the member directly in Discord.
If only the server owner’s nickname is unchanged, that is a Discord platform limitation; use an appropriate manual nickname if community policy requires one.
If profile refresh triggers an automatic Roblox rank change and reports a connection error, inspect Settings → Roblox Cloud. Reauthorization restores the community integration; changing a member's verified account is a separate action. Temporary refresh or provider failures may recover without reconnecting. See Roblox connection errors.
Check a group nickname
Confirm Settings → Verification → Automatically update nicknames is enabled, the bot has Manage Nicknames and is above the member, and the member does not have the Bypass role. Test with a verified non-owner account. Automatic roles can be disabled for nickname-only updates.
| What you see | What to check |
|---|---|
| The community format is used | The selected Roblox account must belong to a bound group with a non-blank Group nickname format, and the plan must include group binds. Rank prefixes alone do not select a group format. |
| Another group's format wins | Higher Nickname priority wins among eligible formats; equal priorities use the lowest Roblox group ID. |
| The expected prefix is missing | Check Nickname prefix for the member's exact rank in the selected external group and use %BINDRANKPREFIX% in the format. %RANKPREFIX% uses the community being updated. A blank prefix adds no text. |
| A saved change has not appeared | Run one member update after saving. The group-bind editor does not immediately rename members. |
| The old nickname remains during a service failure | Failed bind or required membership lookups skip the nickname update. If the selected format uses %ROBLOXDISPLAYNAME%, an unavailable display name also preserves the nickname instead of inserting N/A. Formats without that variable can still update when only the display-name lookup fails. |
When only nickname synchronization needs bind data, a lookup failure skips the nickname while independent profile and progression work can continue. If role synchronization also needs that data, Unable to fetch group binds stops the affected verified member's update before changing roles. Granting only Manage Nicknames does not enable XP or boosting-perk changes.
Review the nickname selection rules before changing priorities or templates.
When to retry
Retry after configuration is saved or after a short external-service delay. Do not repeatedly update many users until one test member succeeds.
Still failing?
Contact Clan Labs support when the correct account, rank, bind, permissions, and hierarchy are confirmed but the result remains stale.
Include community and server IDs, Discord and Roblox user IDs, current Roblox rank, exact /update fields, bind type, timestamp, and redacted role-order screenshot. For nickname issues, include the bound group IDs, formats, priorities, and the selected external rank's prefix.