"The Application Did Not Respond" on Discord: What It Means and How to Fix It

You type a slash command, press Enter, and instead of an answer Discord shows one short line: The application did not respond. Press a button on a bot's message and you may get its cousin instead: This interaction failed.

Both look alarming and both are vague. Neither says what broke or what to do next. This guide explains them in plain words, for members who just want the command to work and for the admins who get asked about it.

What does "The application did not respond" mean?

On Discord, "application" is another word for an app, and almost every app you meet in a server is a bot. So the message simply means: the bot did not answer.

Every time you use a slash command, press a bot's button or pick something from its menu, Discord passes that action to the bot and waits for a reply. Discord calls this an interaction. The rest of this guide just calls it a command or a click.

The waiting has a strict limit. Discord's developer documentation says a bot must send its first response within 3 seconds. That first response can be the real answer, or a loading state that tells you the bot is working on something slow. After a loading state, the bot has up to 15 minutes to send the real answer.

When those 3 seconds pass with nothing, Discord stops waiting for good. Even if the bot finishes a moment later, its answer can no longer be delivered to that command. That is why trying again often works: the new attempt gets its own fresh 3 seconds.

The message comes from Discord, not from the bot. A ticket bot, a music bot and an application bot all produce the same line when they miss the window. Seeing it says nothing about whether a bot is good or bad, only that this one answer did not arrive in time.

Is "This interaction failed" the same thing?

Same cause, different place. The wording depends on what you used:

There is one extra cause that only applies to buttons: old messages. Some bots only listen to the buttons they posted since they last started. Press a button on a message from before a restart and nothing is listening for it any more, so Discord shows "This interaction failed". Running the command again, or using a newer message, usually fixes it.

Our guide to enabling your DMs to apply mentions this error in passing. Here is the full picture.

Why would a bot not answer in time?

Five reasons cover nearly every case:

1. The bot is offline or restarting. Bots restart for updates and after crashes. While one is down, nothing hears your command.
2. Discord itself has a problem. When Discord's own service struggles, answers from every bot can fail to arrive, however healthy each bot is.
3. The bot is overloaded. A busy evening, a slow database or an outside service it waits on can push it past 3 seconds. Well built bots show a loading state first to buy time, but not every bot does it for every command.
4. It is missing a permission in that channel. If the bot cannot see the channel or post in it, the step it needs can fail, and depending on how the bot handles that, you may get no answer at all.
5. An old button. As above: a button from before the bot's last restart may no longer be listened to.

Only the last two have anything to do with your server. The first three are on the bot's side or Discord's, and waiting is the fix.

What can you do as a member?

Not much can be fixed from your side, and that is the good news: it is rarely you. Try these in order:

If a command is missing from the list when you type /, that is a different thing. Discord hides commands you are not allowed to use, so ask staff whether that command is meant for your role.

What should a server admin check?

Admins can see what members cannot. If the error keeps coming back, or only happens in your server, work down this list:

A quick way to tell a permission problem from an outage: try the same command in a channel where the bot clearly works. Works there and fails here: it is that channel. Fails everywhere: it is the bot or Discord.

Which message is which?

Here is every message you are likely to meet, side by side. The last four are about Mico, and the quoted ones are Mico's exact words.

The pattern to remember: when Mico can tell what went wrong, it says so in its own words. Discord's generic line means no answer came back at all.

Does Mico ever show "The application did not respond"?

Yes. The message comes from Discord, so any bot can get it, Mico included. With Mico it nearly always means one of two things: Mico is restarting, or Discord is having trouble.

Two quick ways to check:

• The status page. micoapp.io/status shows whether the bot in Discord, its database and the website connection are answering, with 90 days of uptime and every incident, refreshed every 30 seconds. Mico runs in parts called shards, each looking after a group of servers. When only one is reconnecting, the page says "Some shards are reconnecting. Most servers are not affected."
• The /ping command. If Mico answers it, Mico is up. It shows how fast Discord is answering, how long its own answer took, and whether its database answers.

The full list is in Mico's commands. What a restart does not do:

• Panels keep working. The Apply button on a panel and the Accept and Deny buttons on a review message are tied to the panel and the application, not to the moment they were posted. After a restart they work again by themselves. You never need to repost a panel.
• A sent application is not lost. If Mico restarts just after someone presses Send, it finishes the job when it is back: the AI score and the review message for your team.
• Saved answers stay saved. Each answer is stored as soon as the applicant enters it. Someone halfway through can type /application in their DMs with Mico once it is back and continue at the question they were on. If the last answer showed an error, type that one again.

When should you ask for help?

If the status page says Mico is running, /ping answers, the channel permissions look right and you still get the error, tell us. Join the Mico support server and include:

• the server, and the command or button that failed
• the channel it happened in
• roughly when, and how often
• the code, if Mico showed one under its message

That last one matters most. Mico's error cards, like the missing permission one above, show a short code under the message, and quoting it tells the team exactly where to look.

If you see the same error with a different bot, that bot's own support server is the right place to ask: only its team can see why it did not answer.