Track and recover Roblox operations
Check queued rank and join requests, distinguish automatic correction from administrator review, and avoid duplicate changes.
Last updatedOpen Roblox operations in community management, or follow Check status from a Discord response. This view tracks requests from the dashboard, Discord, and integrations. Your access determines which requests and actions are visible.
Read a request
Check the member, requested action, status, and explanation together. A requested rank on a card is the intended destination, not proof that Roblox applied it. Use the available page controls to find a request, Refresh for a fresh view, or Auto-refresh to keep watching progress.
| State or message | What it means and what to do |
|---|---|
| Queued | The request is saved and waiting for capacity. Do not submit another copy. |
| Running | Processing is underway; the result is not confirmed. |
| Checking Roblox outcome | Clan Labs is checking an uncertain sent request. Wait for its result before another change. |
| Completed | Roblox confirmed the requested result. Check the member's current state if another action may have followed it. |
| Cancelled or expired | Read the explanation for confirmation that unsent work cannot run later. Neither state undoes an earlier completed change. |
| Needs review | An unresolved request protects this member while an administrator checks it. Other members can continue processing. |
| Automatically correcting the member's Roblox roles | Managed recovery is active. Allow it to finish rather than starting manual review. |
Understand a failed request
Expand Support details on a failed request to copy its Request ID and Failure code. Only recognised codes are displayed; unavailable means no safe code is available. Older adapter-rejected records may not retain the original reason. A failure message alone does not prove that Roblox made no change.
| Explanation | What to check |
|---|---|
| Discord access denied | Ask an administrator to check the bot's server membership and access to the requesting member. |
| Requester permission revoked or account changed | Review current community permissions and the requester's verified Roblox account. |
| Requester or target blacklisted | Review the named person's access and the applicable blacklist. |
| Hierarchy changed or rank locked | Check the requester, target, and both current and destination ranks. |
| Rank is no longer adjacent | Refresh the current rank before a new promotion or demotion. |
| Self-action forbidden | Ask another authorised member to review the change. |
| Unknown failure | Check the member's current Roblox rank or membership, then contact support with the request ID. |
Correct the condition named by the message before retrying. Permanent access or authorization failures need that access restored; repeated submissions do not fix them. A Discord access failure does not by itself require reconnecting Roblox.
Let automatic rank recovery finish
When a rank change only partly completes, Clan Labs can automatically correct the member's Roblox roles. Manual-command recovery follows the latest valid rank command; AutoRank recovery uses current progression rules. The service rechecks authority and current state before applying changes.
Managed corrections remain active recovery and cannot be retired through manual review while managed recovery owns them. A newer rank command or progression rule can change the correction that is appropriate, so avoid manual compensation while it is running.
An older unresolved request may instead be retired automatically after checking current Roblox roles. Those roles are preserved and the original outcome remains unconfirmed. Retirement is not a success receipt and does not resend the old request.
Review an unresolved rank request
If Review request is offered, authorised administrators can inspect the requested rank, current Roblox roles, and confirmed change steps. Follow the review dialog only after checking that the displayed current roles are appropriate.
Choose Retire unresolved request only when the review permits it and preserving the current roles is appropriate. Retirement keeps the original outcome unconfirmed in history. A new request is validated against current state. It does not prove the earlier request succeeded or undo its changes. If review is blocked by missing access, a protected workflow, an ambiguous state, or invalid rank configuration, resolve that specific issue or contact support.
Cancel or retry safely
Use Cancel request when offered for queued work. A confirmed cancellation stops unsent work. In-flight means the request has already been sent and its outcome must be checked; it cannot be retracted. An unavailable record or failed cancellation response does not prove that nothing ran.
If a new request says an earlier request needs administrator review, that new request was not submitted. Review the existing request first. If the Roblox connection, permissions, subscription, or community settings changed, resolve the named condition before trying again.
During a planned update, rank and join admission may pause while other pages and commands remain available. Saved work and new requests refused before submission are different cases: follow the response rather than assuming a pause cancelled existing work. For uncertain timeouts, inspect the operation and current Roblox state before replacing it.
If an experience change or event finish triggered AutoRank, its points or awards may already have been saved while the Roblox rank remains pending. Do not repeat the points change or finish to repair the rank.
For a lasting problem, contact Clan Labs support with the community ID, operation ID, target Roblox user ID, requested and current roles, exact status, and time and time zone. Keep credentials out of the report.
See rank-change troubleshooting, durable pending-join reviews, or the separate API operation contract.