Practical Midjourney Troubleshooting Checklist: Fixing Stuck Jobs, Missing Permissions, and Generation Failures

When using Midjourney, the most annoying thing isn’t bad results—it’s when you send a command and nothing happens, the queue gets stuck, or it errors out directly. Below, I break down common Midjourney issues by scenario and give a step-by-step troubleshooting order you can follow immediately. Go through the steps once, and you can usually pinpoint the problem within minutes.

Job stuck in the queue: What to do if it keeps showing Waiting/Queued

If Midjourney seems stuck in the queue, first type /info in Discord to confirm whether your account still has available Fast time or has been switched to Relax. If Fast time is used up, Midjourney will slow down significantly or even sit in the queue for a long time—this isn’t a malfunction, but waiting caused by quota and mode.

Next, check whether you’re sending commands in a “generation-allowed channel”: some server channels disable bot messages or commands. The most reliable approach is to retry in a dedicated channel on your own server, or use a generation channel on the official Midjourney server, to determine whether it’s a channel-permission issue.

Missing permissions: Missing Permissions / unable to use slash commands

Midjourney relies on Discord permissions. When you see Missing Permissions, focus on two items: whether the bot has permission to Send Messages and Use Application Commands (slash commands). If you’re using Midjourney in someone else’s server, ask an admin to grant the necessary permissions for that channel, or move you to a channel where the bot is allowed.

In addition, some servers restrict external application commands or mute bots; you can’t change these restrictions on your end. The fastest way to verify is to go to another server/channel and send /imagine with Midjourney—if it works there, it’s not an account issue.

Generation fails or doesn’t display: you get a receipt message but can’t see the image

If Midjourney generated an image but you can’t see it, first rule out client display issues: refresh Discord, switch networks, and disable browser extensions (especially ad blockers/script plugins). If it doesn’t show in the web version, open the same channel in the Discord desktop app or mobile app—this usually quickly confirms whether it’s a rendering issue or the job didn’t succeed.

If there’s a generation message in the channel but the image loads as a gray placeholder and fails, a common cause is an unstable connection to Discord/CDNs. You can try changing DNS, switching to a more stable network environment, or directly checking the same job in the Midjourney web gallery to cross-verify whether the job actually completed.

Parameter or prompt errors: Invalid parameter / incorrect command format

Midjourney is very strict about parameters. When you see Invalid parameter, first delete the entire parameter section at the end of the prompt and resend with only plain text to confirm basic functionality. Then add parameters such as --ar, --stylize, --chaos back one by one—this usually helps you quickly find which parameter is misspelled or out of range.

When copying someone else’s prompt, it’s also easy to include “invisible characters” or Chinese em dashes, causing Midjourney parsing to fail. It’s recommended to manually retype the two hyphens -- rather than pasting special symbols.

Final step: confirm service status and account status

If Midjourney fails in multiple channels and /info returns abnormal results or doesn’t respond, suspect a Discord-side outage or service fluctuation. First check whether Discord can send messages normally and whether voice is stable, then check Midjourney’s official status page/announcement channel to confirm whether maintenance is in progress.

If only your Midjourney is abnormal while others are fine, first check whether you accidentally logged into a different Discord account, switched to the wrong server identity/role, or whether your subscription status has lapsed and restricted features. Save a screenshot of Midjourney’s /info, then contact the appropriate support channel—this will help the issue get identified faster.