When generating images with Midjourney, the most common sticking points aren’t prompts—they’re commands not responding, jobs stuck in queue, and images that aren’t sharp. Below, I break down the high-frequency issues. Follow the steps to self-check, and in most cases you can pinpoint the cause on the spot.
No response to commands: What to do if /imagine doesn’t respond
When using Midjourney in Discord, first confirm that the channel where you sent the command allows the bot to speak (common issues are permissions being turned off or the channel being set to read-only). If you’re using Midjourney in DMs and don’t see command suggestions above the input box, go to a server’s newcomer channel and try once to make sure the bot is online.
Also, /imagine must be followed by a prompt; sending only “/imagine” may sometimes be treated as an incomplete command. If there’s still no response, log out of Discord and log back in, then return to the same channel and resend it—many “fake freezes” are simply the client state being out of sync.
Jobs always queued: The queue is long or stuck waiting
A queue in Midjourney usually isn’t because you did something wrong—it’s because server load is high or you’re currently in a slower generation mode. First, go to /settings and check whether you switched to Relax (slower). If you need faster results, switch back to Fast (if your plan/credits allow it).
If a Midjourney task shows as submitted but no image appears for a long time, don’t keep clicking and resubmitting; repeating the same prompt just piles up the queue. A more reliable approach is to wait 1–2 minutes, then refresh the job list on the web interface to confirm whether it has already generated and landed in your history.


