Discord troubleshooting
The bot says it is starting up
Section titled “The bot says it is starting up”The runtime is loading configuration or synchronizing commands. Open Dashboard and check the status pill. If it remains starting for longer than a normal deploy, check Logs & Activity, then use Restart. Use Provision / Deploy when the runtime has not been created or a deployment has failed. Do not keep sending commands while it is starting; wait for the status to settle and retry once.
/admin is missing
Section titled “/admin is missing”Confirm the guild ID is in the instance’s admin guild list and your user or role is configured. Reopen Discord’s command picker after a runtime restart. Admin guilds receive an immediate scoped command sync; other commands may rely on global propagation.
Autocomplete shows the wrong collectible
Section titled “Autocomplete shows the wrong collectible”Do not reuse a selection from another instance or type a stale numeric value. Clear the field and choose a fresh suggestion. Every autocomplete result is scoped to the current instance.
The bot is online but silent
Section titled “The bot is online but silent”Check channel permissions, the instance status, and runtime logs. Confirm the bot can view the channel, send messages, embed links, and attach files where applicable.
A setting did not take effect
Section titled “A setting did not take effect”Look for the bottom You have unsaved changes bar. Press Save Changes, then test again. A replacement token or privileged-intent change needs a Dashboard restart. A command-group rename needs Dashboard’s Sync commands. A spawn rule only affects future spawns, not a spawn already on screen.
An import failed
Section titled “An import failed”Open Data, find the job in Recent jobs, and press Log. Read the actual error before pressing Run again. Check the selected instance, file type, and source/destination combination. Make a manual backup before retrying a migration that could alter live data.