Midjourney Troubleshooting: Jobs Stuck on Running, Download Failures, and Permission Fixes

When creating images, the most annoying thing isn’t waiting in line—it’s that you’re clearly being charged GPU time yet nothing ever comes out. This article troubleshoots Midjourney issues in the order I most often use: platform first, then account, and finally local. It focuses on stuck jobs, images that won’t open / downloads that fail, and Discord permissions and login authorization issues. Follow the steps one by one and you can usually pinpoint the cause within a few minutes.

Start Midjourney troubleshooting: platform status and account restrictions

Before you start Midjourney troubleshooting, first rule out platform instability: open status.midjourney.com to see whether there are any generation- or login-related incidents. If the status page shows an issue, don’t keep retrying—failed jobs can pile up easily. It’s simpler to wait for recovery and then submit again.

Next, confirm whether your account is usable: an expired subscription, changes to queue policies, or triggering security/risk controls can all lead to “you can log in but can’t generate images normally.” You can first test by generating a small image with the shortest possible prompt to avoid misjudging a complex job as a system problem.

Jobs stuck on Queued/Running or directly Failed: handle it faster like this

If a job is stuck on Queued/Running, Midjourney troubleshooting generally recommends “reducing load” before retrying: shorten the prompt, reduce the number of reference images, and disable high-consumption parameters first. Many “stuck” cases aren’t because you wrote something wrong, but because jobs are more likely to time out under heavy load.

If the job shows Failed, first check whether you used unsupported links or inaccessible image sources—such as cloud drives/social platforms that require login to view. Switch the reference image to a public direct link, or simply re-upload the image and submit again; the success rate will improve noticeably.

Image preview looks fine but won’t open / download fails: most likely a browser issue

For this kind of Midjourney troubleshooting, I usually start with the browser: first force-refresh the page, then clear the site cache and cookies. If you have ad blockers or privacy extensions installed, they may also be blocking requests to the image domain—temporarily disable them and try again.

Another frequent culprit is restrictions on “third-party cookies / cross-site tracking,” especially when logging in on the web. Change your browser’s third-party cookie setting to Allow (or add exceptions for Midjourney and Discord), then log in again; this usually fixes both preview and download issues at the same time.

Discord shows no permission / interaction failed: check permissions and DM settings

When you see prompts like “Missing Permissions” or “You are not allowed to use this command” in Discord, Midjourney troubleshooting should start with channel permissions: are you using it in a channel where bots are allowed, and do you have permission to speak/use application commands? If it’s a private server, confirm the bot was added correctly and that its permissions aren’t being overridden by roles.

If it says “This interaction failed” or commands don’t respond, first check whether you’ve disabled DMs from the Midjourney bot, or whether the server is blocking bot messages. Turn on DMs with the bot and try again in a channel that works on the official server—this is often more effective than blindly reinstalling the client.