A temporary Roblox, Discord, or Clan Labs service problem occurs
Retry safely, avoid duplicate writes, and collect useful evidence during a Clan Labs dependency outage.
Last updatedA 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.
Fix it
- Save the exact error and timestamp.
- Check whether read-only pages or commands work.
- Determine whether one user, one community, or multiple services are affected.
- Inspect the target state directly before repeating a write.
- Confirm the message does not name a missing permission, scope, plan, or credential.
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 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. For API 429, check error.code: honor Retry-After when supplied for rate limiting. Scheduler queue-full responses can omit it; reduce submissions and use bounded exponential backoff, keeping the same Idempotency-Key for asynchronous Roblox submission.
For a community export failure, check fresh Discord verification, ownership of the included divisions, other community operations, and the download's retry interval. Verify that the ZIP opens and contains its manifest; a download that started can still be incomplete. See community download recovery.
Still failing?
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 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.