How to Fix Discord Error ‘Application Did Not Respond’ on Slash Command

When you type a slash command in Discord, the app sometimes shows the error “Application Did Not Respond.” This happens when the bot or integration fails to reply to Discord’s interaction request within three seconds. Discord requires all slash commands to respond within this time limit, or the interaction times out. This article explains why the error occurs and provides step-by-step fixes for server owners, bot developers, and regular users.

Why Discord Shows “Application Did Not Respond” for Slash Commands

Discord’s slash command system works by sending an “interaction” to the bot’s server when a user types a command. The bot must reply to this interaction within three seconds. If the bot is offline, slow, or blocked by permissions, Discord cannot get a response and shows the error. The three-second limit exists to keep the user interface responsive. If the bot needs more time to process the command, it must use a deferred response to tell Discord to wait.

Common Root Causes

The error can come from three main sources: the bot’s server is down or overloaded, the bot lacks required permissions in the channel, or the bot’s code does not handle the three-second window correctly. Network issues on the user’s side can also cause the interaction to fail before reaching the bot.

Steps to Fix “Application Did Not Respond” Error

Follow these steps in order. Start with the simplest checks and move to more advanced fixes if needed.

Step 1: Check Bot Status and Permissions

1. Open Discord and go to Server Settings
   Right-click your server name in the channel list and select Server Settings. If you are not the server owner, ask the owner to check permissions.
2. Navigate to Integrations
   In the left sidebar, click Integrations. Find the bot that is not responding and click Manage.
3. Verify the bot has the “Use Slash Commands” permission
   Under Permissions, scroll to the Text Permissions section. Ensure Use Slash Commands is enabled. If it is disabled, toggle it on and click Save Changes.
4. Check if the bot is online
   Look at the bot’s profile in the member list. If it shows a gray icon, the bot is offline. Contact the bot developer or check the bot’s status page.

Step 2: Test the Command in a Different Channel

1. Open a text channel where you know the bot works
   Try a general or bot-commands channel. Some channels have restricted command permissions.
2. Type the same slash command again
   If the command works in one channel but not another, check the channel-specific permissions in Channel Settings > Permissions.

Step 3: Clear Discord Cache and Restart

1. Close Discord completely
   Right-click the Discord icon in the system tray and select Quit Discord.
2. Open the Run dialog
   Press Windows key + R, type %appdata%/discord, and press Enter.
3. Delete the Cache folder
   Find the folder named Cache, right-click it, and select Delete. Do not delete any other files or folders.
4. Restart Discord
   Open Discord again and test the slash command.

Step 4: Check for Bot Rate Limits

1. Wait 30 seconds after the error
   If you or others sent many slash commands quickly, Discord may have rate-limited the bot. Wait 30 seconds before trying again.
2. Use a single command and observe
   Type one slash command and wait for the response. If it works, the previous failure was likely due to rate limiting.

Step 5: Bot Developers — Implement Deferred Response

1. Add DeferReply at the start of the command handler
   In Discord.js, use interaction.deferReply() to acknowledge the interaction immediately. This tells Discord to wait while the bot processes the command.
2. Set the ephemeral flag if needed
   Use interaction.deferReply({ ephemeral: true }) for commands that should only be visible to the user.
3. Respond within 15 minutes after deferring
   After deferring, you have up to 15 minutes to send the actual response using interaction.editReply(). If you do not respond within 15 minutes, the interaction expires again.

If Discord Still Shows the Error After the Main Fix

The Bot Goes Offline After Server Boost Expires

Some bots require a boosted server to use certain features. If your server’s boost level drops, the bot may lose access to premium endpoints and fail to respond. Check the bot’s documentation for boost requirements. If the bot is a custom bot, ensure the bot token is valid and not expired.

Command Works on Desktop but Not Mobile

Discord mobile apps sometimes have outdated slash command caches. Force close the Discord mobile app, reopen it, and try the command again. If the issue persists, uninstall and reinstall the Discord mobile app.

Error Only Occurs with Slash Commands, Not Chat Messages

This indicates the bot is online but not properly handling slash command interactions. The bot developer must check the interaction handler code. The bot may be using an outdated library that does not support slash commands. Update the bot’s Discord API library to the latest version.

Discord Interaction Response Methods: Defer vs Instant

Item	DeferReply (Deferred Response)	Instant Reply (Direct Response)
Time limit to acknowledge	3 seconds	3 seconds
Time limit to send content	15 minutes after defer	Must be within the same 3 seconds
Use case	Commands that take longer than 3 seconds to process	Commands that can respond instantly
Ephemeral support	Yes — use deferReply({ ephemeral: true })	Yes — use reply({ ephemeral: true })
Error risk	Low if you respond within 15 minutes	High if processing takes more than 3 seconds

Now you can fix the “Application Did Not Respond” error by checking bot permissions, clearing your Discord cache, or implementing a deferred response in your bot code. If you are a server owner, verify that the bot has the correct permissions in each channel. If you are a bot developer, add DeferReply to all command handlers that perform database lookups or API calls. For a more robust setup, consider using Discord’s autocomplete feature to reduce command processing time.