How do I fix broken buttons or slash-command (/register) errors?
Slash commands that won't register and buttons that don't respond are frustrating — but the good news is they're almost always fixable on your side. This article walks through the usual causes and how to clear them.
Why this happens
Slash-command and button issues are almost always in your code or registration, not the host. Discord needs your commands registered correctly and your bot configured with the right intents and permissions — when one of those is off, buttons and commands go quiet.
How to fix it
- Make sure your command-deploy / register script ran successfully — check the Console output for its result.
- Confirm your bot has the right intents and permissions in the Discord Developer Portal.
- Re-run your register step and then Restart the bot.
Tip: Global slash commands can take time to propagate across Discord, while guild commands register instantly — use guild commands while testing for immediate feedback.
Frequently asked questions
My register script shows no errors but commands still don't appear. If they're global commands, give them time to propagate. To confirm your setup works right away, register them to a test guild instead.
Buttons worked yesterday and stopped today. Check the Console for errors when the button is pressed, and confirm your interaction handler is running and your intents haven't changed.