My Discord bot token stopped working
A bot held for an invalid Discord token cannot restart by itself. Its owner must replace the token on the bot page. Keep the token private throughout the repair.
Open dashboardBefore you start
- Sign in to the Build Discord Bots account that owns this bot and the Discord account that owns its application.
Why the token stopped working
Reset Token invalidates the old token. Discord may also revoke an exposed token after a leak. If the application was deleted, its old token cannot restore it; you need a new application and bot setup instead.
Recognize the dashboard warning
On the dashboard, the bot card says “Needs attention” and offers “Fix it”. The recovery alert says “Recovery is paused for” followed by your bot’s name. Follow “Fix it” or open that bot.
Reset the token in Discord
Open Discord Developer Portal → Applications → your existing application → Bot → Reset Token → “Yes, do it!”. Confirm your password or two-factor authentication if asked, then choose Copy right away. Use the application for this bot; creating a different app does not restore the original bot. There is no Add Bot step.
Paste the new token on the bot page
On the bot page, find “Replace this bot's Discord token and start it” above the diagnostic checklist. Paste the new token into “New bot token”, then choose “Replace token and start”. This checks the token with Discord and attempts to start the bot. You do not need to find the token field in Settings for this repair. If this section is missing, open “Support” from the sidebar and ask for help with the hold; do not include your token.
Check the result
On success, the page says “Token verified and bot started”. If it says “Discord still refused this bot token.”, reset and copy the token again from the correct application. Other errors, such as a hosting or plan limit, can still prevent starting; follow the displayed error and check the bot status. If you cannot access the application, ask its owner to help.
Frequently asked questions
Will pressing Start fix an invalid token?
No. The invalid-token hold needs a valid replacement token before the bot can start.
