You type a slash command or press a button, Discord shows a loading line for a moment, then a small grey message: "The application did not respond". The same error shows up as "Interaction failed" on buttons and menus. It looks like Discord is broken. Most of the time it is the bot.
What the message means
Every slash command, button, select menu and modal is an interaction. Discord sends it to the app that owns the command and waits. Discord's developer docs say the app must send an initial response within 3 seconds of receiving the event. If it misses that window, the interaction token is invalidated and you see the error.
Apps that need more time are supposed to defer. A deferred reply shows the "is thinking" loading state, and the app then has 15 minutes to edit in the real answer, because interaction tokens stay valid for 15 minutes. A bot that does slow work first and replies second will fail whenever that work takes more than 3 seconds.
Checks for server owners
You can not fix someone else's code, but you can find out quickly whether the problem is yours, Discord's or the bot's.
- Is the bot online? Look for it in the member list. Offline or missing means it crashed, was kicked, or its host is down.
- Is Discord having a bad day? Open discordstatus.com. If several bots fail at the same moment, an incident there is the likely cause.
- Reload Discord. Press Ctrl+R on desktop or restart the mobile app. Discord checks command versions, rejects outdated global commands and reloads them, so a stale command list clears up after a refresh.
- Try a simpler command. If
/helpanswers but/reportdoes not, that one command is slow or broken. - Wait a minute and retry. Bots restart after updates. A short gap usually means a deploy.
- Report it with details. Bot developers fix this fast when you give them the command, the server, the time and a screenshot.
Fixes for developers
If it is your bot, the cause is nearly always one of these.
| What happens | Why it fails | Fix |
|---|---|---|
| Command calls a database or API before replying | The call takes longer than 3 seconds | Defer first (response type 5), then edit the reply when the work is done |
| Handler throws an error | No response is ever sent | Wrap handlers, log the error and reply with a short error message |
| Buttons stop working after a while | The component is still there but the bot no longer handles its custom_id (for example after a restart) | Route components by custom_id from persistent handlers, not in-memory collectors only |
| Nothing arrives over the gateway | An Interactions Endpoint URL is set in the Developer Portal. Gateway and HTTP delivery are mutually exclusive | Remove the endpoint URL, or answer the HTTP requests at that URL |
| HTTP bot times out | The endpoint does slow work before returning | Return 200 with the response body, or send the callback and return 202 with no body |
A good habit: acknowledge every interaction in the first few lines of the handler. Defer when there is any chance of slow work, and use the "update message" defer (type 6) for buttons so the user does not see a loading state.
If it is a VaultCord command
VaultCord's commands are /verify-embed, /pull, /info, /backup, /massrole, /unrole. They run on your own branded bot, which stays online 24/7: 1 bot on Free, 3 on Premium, unlimited on Plus.
If one of them shows "The application did not respond", check discordstatus.com first, then message support at help.vaultcord.com. Everything the commands do can also be done from the web dashboard and the iOS and Android apps, so a stuck command never blocks a backup or a pull.
Open the web appQuestions people ask
Why does my Discord bot app say it is not responding?
Discord shows "The application did not respond" when an app does not answer a slash command, button or menu within 3 seconds. The bot may be offline, restarting, overloaded, or its code may have crashed or skipped the reply.
How long does a Discord bot have to reply to a command?
3 seconds for the first response. A bot that needs longer can defer, which shows a loading state, and then has 15 minutes to send the real answer with the same interaction token.
Is "The application did not respond" a Discord outage?
Sometimes. If many bots fail at once, check discordstatus.com. If only one bot fails, the problem is almost always on that bot's side.
Can I fix it if I am not the bot's developer?
You can rule out the simple things: check the bot is online, reload Discord so outdated commands refresh, and try again a minute later. If it keeps happening, report it in the bot's support server with the command you ran and the time.