Midjourney Troubleshooting Guide: Stuck in Queue, Generation Failures, and Permission Errors

When generating images with Midjourney, the most common point of failure isn’t the prompt—it’s issues like “commands not responding, endless queueing, or sudden permission/subscription warnings.” Below I’ll break it down by symptom and give you a fast-to-slow troubleshooting sequence. Follow it and you can usually pinpoint the problem and get back to generating within minutes.

No response to commands: first confirm where you’re sending it and your permissions

When using Midjourney in Discord, if you type /imagine in an unsupported channel or in a channel where you don’t have permission to speak, it can look like “nothing happens.” First confirm you’re in a Newbies channel on the official server, or that you’ve correctly invited the Midjourney Bot into your own server, and that the channel permissions allow you to send messages and use application commands.

Also check whether you accidentally sent the command in DMs while DMs are closed, or whether the bot is temporarily offline. The easiest approach is to switch to another official channel and try the same /imagine again; if it still doesn’t respond, logging out of Discord and back in often fixes command menus that aren’t refreshing.

Endless queueing or stuck on Queued: usually caused by mode and quota

Seeing “Queued/Waiting to start” in Midjourney is very common. It’s usually not an error—it’s queue congestion or a mismatch with your mode. First use /settings to confirm whether you’re in Relax mode (slower) or Fast mode (faster), and then consider whether it’s peak time; switching to a less crowded official channel may also get you into the queue faster.

If you notice the queue time suddenly becoming unusually long, check whether your Fast hours have run out or whether your account status is restricted. On Midjourney’s web account page you can usually see your usage and task status; shortening the same prompt and reducing concurrent jobs can also reduce the chance of it “looking stuck.”

Generation failed or rejected: start with the prompt and uploaded links

Common reasons for “generation failed” in Midjourney include the prompt triggering safety restrictions or referenced image links being inaccessible. First remove potentially sensitive words from the prompt and switch to a more neutral description; if you used an image prompt, make sure the image is a publicly accessible direct link and hasn’t expired or been access-restricted.

Parameter errors can also cause Midjourney to reject a job immediately, such as misspelling --ar, --s, or --chaos, or using values out of range. The most reliable troubleshooting method is to keep only the base prompt and see whether it generates, then add parameters back one by one to quickly identify which part is triggering the problem.

Subscription/permission warnings: verify your account and login state

If you see messages like “subscription required” or “no permission to use,” first confirm that the Discord account you’re currently using is the paid one, and that you haven’t been tripped up by switching between multiple accounts. Especially when you’re logged in on both mobile and desktop, Midjourney may be recognized as different accounts on different devices—showing as usable on the web but not in Discord, or vice versa.

If you’re sure the account is correct, try re-authorizing the app in Discord (or rejoining the server), and then clear the web login state and log in again. If it still doesn’t work, go to the Midjourney account page to verify the subscription is active; keep the original error message and screenshots, and submit them to official support—this usually helps them locate the issue faster.