Midjourney Troubleshooting: Fixing Moderation Failures, Unresponsive Commands, and Rate Limits

When creating images, if your commands won’t send, the queue doesn’t move, or you’re told the prompt was blocked by moderation, it’s usually not because you “did something wrong.” Below is a set of Midjourney troubleshooting steps organized by the most common scenarios. Identify the cause first, then fix it—this can save you a lot of pointless retries.

Unresponsive command: /imagine sent but no receipt at all

Start with the most basic Midjourney troubleshooting: confirm the channel where you’re sending the command allows the bot to work. Prefer the official recommended image channels, or a channel in your own server where the bot has been added. If the slash-command menu doesn’t appear at all, it’s usually because Discord hasn’t fully loaded permissions—refresh the client, log out and back in, or reopen it once on desktop for a more reliable fix.

If only you can’t see the receipt, check whether you accidentally muted the bot or hid its messages, or whether the channel filter is set to show only “Pinned/Followed.” If it still doesn’t work, check the status page for service fluctuations (status.midjourney.com). When the service is having issues, repeatedly retrying will only make things slower.

Prompt blocked: Blocked, moderation failed, or no image generated

The core of this type of Midjourney troubleshooting is “remove first, then add back”: delete any parts of the prompt that might trigger moderation (sensitive descriptions of people, explicit terms, hate/harassment, gory details, etc.). Once it generates successfully, add details back step by step. Also watch out when using image references—external links that redirect, require login, or come from short-link platforms often cause fetch failures.

If you see “Invalid link / unable to read image,” replace the image with a publicly accessible direct link, or reupload it to Discord and reference it from there. Don’t change too many things at once, otherwise it’s hard to tell which part triggered the block—this is the most common Midjourney troubleshooting mistake.

Queue stuck and endless waiting: Job queued, progress not moving

Three Midjourney troubleshooting steps first: click “regenerate/retry” once on the same job and see whether a new job is created; if not, send it in a less crowded channel; finally, restart the Discord client. Queuing during peak hours is normal, but if all your jobs are stuck, first check whether your network is unstable for Discord voice/media connections—try another network or disable your proxy and try again.

Also don’t overlook account status: if your subscription has expired or permissions changed, it may look like “commands can be sent but no images are generated.” Open your Midjourney website account page to confirm your subscription and quota display are normal—this is a crucial Midjourney troubleshooting step.

Rate limiting: Too many requests, longer cooldown time

When you see a rate-limit message, Midjourney troubleshooting should go in the opposite direction: reduce concurrency, increase the interval between sends, and don’t spam-click upscale/variations. Break one task into fewer variation needs, or first confirm direction with low-cost rough drafts and then refine—this can significantly reduce how often you trigger it.

If you’re operating in multiple channels or on multiple devices at the same time, it’s easier to trigger rate limits cumulatively. It’s recommended to stick to one channel and one device for the main workflow; stability is higher than “trying everywhere,” and this is also the most effortless Midjourney troubleshooting strategy.