A temporary Roblox, Discord, or Clan Labs service problem occurs

SymptomCopy link to Symptom

A normally working action times out, data cannot refresh, Clan Labs reports a service is temporarily unavailable, or Discord says The bot is updating. Please try that interaction again in a few seconds.

Most likely causesCopy link to Most likely causes

• Roblox, Discord, Clan Labs, or a network path is temporarily unavailable.
• The bot is being updated and cannot accept that interaction momentarily.
• An external write completed but its response was lost.
• A browser or Discord client has stale cached state.
• A configuration error is being mistaken for an outage.

Diagnostic checksCopy link to Diagnostic checks

1. Save the exact error and timestamp.
2. Check whether read-only pages or commands work.
3. Determine whether one user, one community, or multiple services are affected.
4. Inspect the target state directly before repeating a write.
5. Confirm the message does not name a missing permission, scope, plan, or credential.

ResolutionCopy link to Resolution

For a bot update, wait a few seconds. For a dependency problem, pause changes, keep existing configuration, and use read-only checks until the service returns. Refresh or sign in again only when the session itself appears stale.

Do not rotate keys, loosen permissions, recreate communities, or repurchase subscriptions merely to test an outage.

When to retryCopy link to When to retry

Retry a read after a short delay. Before retrying a rank, suspension, pending-join, event-finish, subscription, transfer, or other write, fetch the current state so the first attempt is not duplicated. Use Retry-After for API 429 responses.

Contact supportCopy link to Contact support

Contact Clan Labs support if the problem persists after the dependency recovers, affects only one community, or leaves a write in an uncertain state.

Include this informationCopy link to Include this information

Include affected service, community and user/resource IDs, exact action and error, timestamp and time zone, whether reads work, current target state, and request correlation information if available. Never include credentials.