> What the status dot, intent warnings and credential checks on a RestoreCord bot card mean, and how to get an offline custom bot back online in minutes.

Source: https://restorecord.app/bot-health

# Reading your RestoreCord bot card when something's off

If verification stops working, the bot is the first place to look. The Bots page in the RestoreCord dashboard tells you exactly what's wrong, as long as you know how to read it.

[Get started free](https://restorecord.com/register)[View pricing](https://restorecord.com/pricing)

Short answer

Open Dashboard → Bots. A green dot means the bot is connected. Fix any intent or redirect URL warning in the Discord Developer Portal, paste regenerated credentials into the bot's Credentials card, then restart the bot.

## Start with the status dot

Each card shows the bot's username, client ID and a live dot. Green means RestoreCord has the bot connected to Discord and it can handle verifications, slash commands and server operations. Anything else means it's time to work down this page.

Bots shared with you through sub-user access also appear in the list, but without their token or edit actions. Only the owner can fix those.

A

### Aurora Gatekeeper

Shared

Aurora Gatekeeper • 123456789012345678

Manage BotInvite Bot

## "Privileged intents are disabled"

Discord rejected the bot's gateway intents, so it restarted without member and message-content events. In the Discord Developer Portal, open your application, go to **Bot** and enable both **Server Members Intent** and **Message Content Intent**. Save, then press **Restart Bot** in RestoreCord.

## Credentials that stopped working

The Credentials card validates the token and client secret against Discord as you type, and a green ring means Discord accepted them. If someone reset the token in the Developer Portal, the old one stops working immediately. Paste the new value here and save **before** you run a backup, restore or pull.

### Bot Credentials

Sensitive information used to authenticate your bot

Bot Token

••••••••••••••••••••••••••••••••

Client Secret

••••••••••••••••••••••••

Valid Redirect URL

## "Invalid Redirect URL"

The callback URL shown on the card is missing from your Discord application's OAuth2 settings. Copy it from the card and add it under OAuth2 → Redirects. For a standard setup that's `https://restorecord.com/api/callback`. With a custom domain, it becomes your domain plus `/api/callback`.

Switching domains? Add the new callback in Discord first and leave the old one until the new domain is active and tested, or live verification links will break halfway through.

## Quick reference

| What you see                    | Likely cause                                                 | Fix                                     |
| ------------------------------- | ------------------------------------------------------------ | --------------------------------------- |
| Dot isn't green                 | Bot disconnected or credentials rejected                     | Check credentials, then Restart Bot     |
| Invalid Token alert             | Token changed, or the bot was deleted or disabled by Discord | Paste a fresh token into Credentials    |
| Privileged intents are disabled | Intents off in the Developer Portal                          | Enable both intents, then restart       |
| Invalid Redirect URL            | Callback missing in OAuth2 settings                          | Copy the URL from the card into Discord |
| Status text didn't change       | Presence updates are delayed                                 | Wait up to two minutes                  |
| Bot in a server you don't know  | Unexpected install                                           | Leave it from Manage Bot Guilds         |

## Presence is cosmetic

Status and activity change how the bot looks in Discord, never what it can do. Choosing Invisible clears the activity text. Updates can take up to two minutes to appear, so don't restart just because the status lags.

## Audit where the bot lives

Under Advanced Settings, **Manage Bot Guilds** lists every server the bot is installed in. Leave any you no longer manage, and investigate any you don't recognise.

## Restart versus delete

1. 1Restart Bot reconnects the bot to Discord. Use it after any credential or intent change.
2. 2Delete Bot removes the bot and every member and server record attached to it. It can't be undone, so detach dependent servers first.

After any fix, verify once with a staff account to confirm the full flow works. More about the rest of the app in the [dashboard tour](https://restorecord.app/dashboard-tour), or go back to the [RestoreCord App home](https://restorecord.app/).

## A two-minute bot health check

1. 1  
### Read the status dot  
Open Bots and confirm each card shows a green dot, which means the bot is connected.
2. 2  
### Clear any warnings  
Fix privileged intent or redirect URL warnings in the Discord Developer Portal, then save.
3. 3  
### Restart and test  
Use Restart Bot after credential or intent changes, then verify once with a staff account.
[Read the bot management docs](https://restorecord.com/docs/guides/bot-management)

## Bot card questions

### 

### 

### 

## Keep every bot green

RestoreCord shows the health of all your custom bots on one page, free on every plan.

[Get started free](https://restorecord.com/register)[View pricing](https://restorecord.com/pricing)
