How to Fix Midjourney " the Application Did Not Respond" Error on Discord

Midjourney's "The application did not respond" error on Discord means the bot failed to catch your slash command within Discord's strict three-second API handshake window. Your account isn't banned, and your prompt wasn't rejected for content violations. The fastest way to clear it right now is moving out of crowded public channels into your Direct Messages with the Midjourney Bot, or unlinking and re-inviting the bot to your private server to refresh its OAuth2 token.

What Is Actually Triggering "The Application Did Not Respond"?

Let's look under the hood of how Discord talks to external AI servers. When you type /imagine and hit Enter, your message doesn't just sit in a chat room. Discord fires an HTTP POST payload (an interaction token) over to Midjourney's backend servers.

Discord has a ruthless rule for bots. That external server has exactly 3,000 milliseconds (3 seconds) to send back an HTTP 200 OK packet saying, "Got the prompt, working on it." If Midjourney's intake router takes 3.1 seconds to reply, Discord kills the handshake dead. It throws the red "The application did not respond" banner on your screen and wipes out the text you just spent five minutes typing.

Why does that three-second window get missed? Half the time, you're sitting in a public #newbies channel where 400 people are spamming commands at the exact same second, choking the local rate limiter. Other times, your local Discord app is holding onto an expired session token in its AppData folder, or your VPN is routing your WebSocket connection through a congested node that drops the return packet.

Real-World Tip: Before you press Enter on a long, complicated prompt during peak hours, press Ctrl + A then Ctrl + C (or Cmd + A and Cmd + C on Mac) to copy your text to the clipboard. When Discord drops a slash command with "The application did not respond," it deletes your entire typed prompt from the chat box. Having it saved on your clipboard saves you from retyping fifty words of lighting and camera parameters from memory.

Proven Fixes for Midjourney "The Application Did Not Respond" Error (Ordered from Easiest to Advanced)

Method 1: Ditch Public Channels and Switch to Direct Messages

If you're still generating images inside the official Midjourney server's #newbies or #general rooms, you're fighting Discord's per-channel rate limit. When dozens of users hit Enter at once, Discord queues the outgoing webhooks, causing yours to miss the three-second timeout.

1. Open the official Midjourney server in Discord and look at the right-hand member sidebar (if it's hidden, click the Show Member List icon resembling two people at the top right).
2. Find the Midjourney Bot near the top of the list and left-click on its name.
3. In the pop-up profile card, click into the Message @Midjourney Bot text box, type /info, and press Enter.
4. This opens a dedicated, one-on-one Direct Message channel between you and the bot.
5. Type /imagine in this private DM chat, click the command pop-up box so the prompt pill appears, paste your prompt, and hit Enter.

How to verify it worked: The bot immediately displays a yellow "Waiting to start..." message inside your DM window within two seconds instead of pausing and dropping the red error banner.

Method 2: Kick and Re-Authorize the Midjourney Bot on Your Private Server

Using your own private Discord server is great for organizing art folders, until Midjourney pushes a backend API update. When they update permissions, the OAuth2 handshake token linking the bot to your private server goes stale. Commands fail instantly.

1. Go to your private Discord server, right-click the Midjourney Bot in the right-hand member list, and select Kick Midjourney Bot. Click Kick again to confirm (you won't lose any previously generated images in the chat history).
2. Click your server name at the top-left corner and go to Server Settings > Integrations > Bots and Apps to make sure Midjourney Bot is completely gone from the list.
3. Now go back to your Direct Messages with the Midjourney Bot (or the official server), left-click the bot's avatar to open its profile, and click the big Add App button.
4. Select Add to Server, pick your private server from the dropdown menu, click Continue, ensure all permission boxes are checked, and click Authorize.
5. Complete the quick CAPTCHA box to finalize the new OAuth2 token.

How to verify it worked: Return to a text channel in your private server and run /settings; if the interactive settings buttons load right away, the token is fixed.

Method 3: Flush Discord's Local AppData Cache and Force a Hard Reload

Discord's desktop app runs on Electron, which means it's basically a disguised Chrome browser. Over weeks of generating heavy four-grid PNG files, its local cache gets bloated and corrupts the scripts responsible for rendering slash command menus.

1. First, try a live socket reset inside the Discord app by pressing Ctrl + R on Windows (or Cmd + R on Mac). Wait for the spinning Discord logo to reload your chats.
2. If the error persists, close Discord completely: look at your Windows System Tray (bottom-right corner by the clock), right-click the Discord icon, and click Quit Discord.
3. Press Windows Key + R to open the Run dialog box, type %appdata%\discord, and press Enter.
4. Inside the folder that opens, locate and delete these three specific folders: Cache, Code Cache, and GPUCache. (Leave everything else alone so you stay logged in).
5. Relaunch Discord from your desktop shortcut and let it build fresh cache directories.

How to verify it worked: Type /prefer remix in your bot chat and press Enter; you'll see an instant confirmation message toggling Remix mode without any lag.

Method 4: Fix the Accessibility Legacy Slash Command Bug

Sometimes people turn on specific accessibility toggles in Discord to change how chat text behaves. One specific setting breaks modern interactive bot menus, causing your prompt to be sent as dead plain text or a malformed API call that Midjourney ignores.

1. Click the User Settings gear icon at the bottom-left of your Discord window (right next to your microphone and headphones icons).
2. In the left sidebar under the App Settings section, click on Accessibility.
3. Scroll all the way down to the bottom of the Accessibility page until you find the Text-to-Speech and Messages toggles.
4. Look for the setting labeled Use legacy chat input. Make sure this toggle is switched OFF (grayed out).
5. Next, click Text & Images in the left sidebar and ensure Preview emojis, mentions, and markdown syntax as you type is switched ON, then press Esc to exit settings.

How to verify it worked: When you type /imagine and hit the Spacebar, a dark pill-shaped box saying prompt automatically wraps around your cursor instead of staying plain white text.

Method 5: Kill VPN Split-Tunneling and Reset Your Network Socket

Discord uses persistent WebSockets over UDP and TCP to keep real-time bot interactions alive. If you're running a VPN (like NordVPN, ExpressVPN, or Cloudflare WARP) or custom firewall rules, packet fragmentation can delay the outbound webhook past the 3-second cutoff.

1. Open your VPN client and disconnect completely—don't just pause it, as background virtual network adapters often keep routing traffic.
2. If you use Discord PTB (Public Test Build) or Discord Canary, switch back to the standard stable Discord client, or open discord.com/app in Google Chrome or Edge to bypass local desktop firewall blocks.
3. Press Windows Key + S, type cmd, right-click Command Prompt, and select Run as administrator.
4. Flush your stale DNS routes and reset the Winsock catalog by typing these two commands, hitting Enter after each:
   ipconfig /flushdns
netsh winsock reset
5. Restart your PC and test Midjourney in the browser or desktop app before turning any VPN back on.

How to verify it worked: Click any existing U1–U4 or V1–V4 button under an older image; the button immediately turns blue with a spinning loading indicator instead of throwing "Interaction failed."

What to Do If Nothing Works (Server Outage vs. Local Client Failure)

If you've moved to DMs, flushed your `AppData` cache, re-invited the bot, and turned off your VPN—yet every single slash command still dies after three seconds—you need to figure out if your local setup is broken or if Midjourney's GPU cluster is literally on fire.

Here is how you separate a local software glitch from a dead backend server in thirty seconds:

• Check the Official Status Channel: Go to the official Midjourney Discord server and click the #status channel at the top left. If the bot bridge is down, the engineering team posts real-time alerts there within minutes.
• Test the Web Alpha Interface: Open your browser and log directly into midjourney.com/imagine using your Discord credentials. Type a prompt into the top creation bar on the website. If the website generates your image smoothly while Discord keeps throwing "The application did not respond," Midjourney's AI GPUs are fine—it's strictly the Discord API bridge experiencing an outage (check discordstatus.com under "API" or "Gateway").
• Check for Stuck Jobs in Your Queue: Occasionally, a bugged job gets permanently wedged in your account's active queue on Midjourney's server, blocking new commands. Open your DM with the bot, type /info, and look at Waiting or Running Jobs. If you see a phantom job stuck running for over 30 minutes, find that specific message in your chat history and react to it with the red ❌ (Cross Mark) emoji to force-kill the process on their backend.

Common Questions From Users

Does "The application did not respond" use up my Midjourney Fast Hours?

No, it doesn't touch your GPU minutes at all. Because the error happens when Discord fails to deliver your command to Midjourney's server during the initial three-second handshake, the GPU cluster never even receives the job. Your Fast Hours are only deducted once a job actually starts rendering at 0%.

Why does Midjourney work on my phone but says "The application did not respond" on my PC?

That's a dead giveaway that either your PC's local Discord `Cache` folder is corrupted, or a background app on your computer (like a VPN, killer network manager, or strict antivirus web shield) is delaying WebSocket packets. Clearing `%appdata%\discord\Cache` (Method 3) or disabling your PC's VPN fixes this mismatch right away.

Why do the U1, U2, V1, V2 buttons say "Interaction Failed" on my older images?

When you click an Upscale or Variation button on an image you generated days or weeks ago, Discord fires an interaction call looking for the original session metadata. If Midjourney updated its bot architecture in the meantime, or if you're clicking fast during a minor server hiccup, the button times out. Copy the image's Job ID (by reacting with the ✉️ envelope emoji to the image), then type /show and paste the Job ID to spawn a fresh, working set of buttons.

Can I get this error if my Midjourney subscription just expired?

Usually, an expired subscription triggers a polite pop-up card from the bot asking you to `/subscribe`. However, if your billing cycle lapsed right in the middle of an active session while Discord's API is lagging, the permission rejection can time out and display "The application did not respond" instead. Run `/info` in your DMs to verify your subscription still shows as Active.