When generating images with Midjourney, the most frustrating issues are jobs not moving, queues being too long, or subscription status not matching. Below, we break down the most common problems and provide a practical troubleshooting order to help you quickly get Midjourney generating normally again.
If a job is stuck or no image is produced, check the queue and mode first
When a Midjourney job gets stuck, first confirm whether you’re in Relax mode or in a peak, congested queue period—wait times can become noticeably longer. It’s recommended to type /info in Discord to check your current mode, remaining Fast time, and job queue status, and confirm it’s not simply “waiting in line.”
If the queue shows the job as completed but you can’t see the image, first check whether you posted in the wrong channel or the message got pushed up by other messages; you can also recover most jobs from the Midjourney web app under “Archive/History.” If there’s still no result, resend with a different prompt and observe whether all jobs fail, to rule out a one-off job anomaly.
If you see “insufficient permissions/can’t use commands,” it’s most likely a Discord settings issue
Midjourney runs based on Discord permissions. A common situation is that you don’t have permission to “Send Messages/Use Application Commands” in a particular server channel. Switch to an official newbie channel or another channel where you’re sure you can speak, then try /imagine to see whether you can invoke Midjourney normally.
If it only fails in one server, contact the admin to grant you the appropriate channel permissions; if it fails everywhere, check whether you accidentally blocked the Midjourney Bot, or restricted app interactions in Discord under “Privacy & Safety.” After fixing it, log out and back into Discord and try the Midjourney command again—this usually restores it.


