Midjourney FAQ: What to Do If the Queue Takes Too Long, How to Recover Missing Works, and How to Handle Blocked Prompts

When generating images with Midjourney, the most frustrating part is often not that you don’t know how to write prompts, but that the queue takes forever, the image suddenly can’t be found, or a blocked-prompt warning makes you give up. Below, these common Midjourney issues are broken down clearly. Troubleshoot step by step, and you can basically solve them on your own.

Queue takes too long and the job won’t move: First confirm whether it’s “actually stuck”

When Midjourney shows a very long queue time, it’s often just normal during peak hours, especially when you submit multiple images in a row. First check whether the job has any progress indicators (such as changes in queue position). If it’s changing, just wait a bit and don’t repeatedly resend the same command.

If the Midjourney job shows no change at all for a long time, try stopping the job and submitting it again, and slightly simplify your prompt to reduce the processing burden caused by overly long descriptions. Another common situation is an unstable network making it “look stuck” on your side—after switching networks or refreshing the page/client, you’ll often find that Midjourney has actually already generated the image.

Can’t find the image / history seems gone: Trace it back from the “generation entry point”

Midjourney images usually aren’t truly “gone”—more often you generated them in a different channel, a different DM window, or a different account, and then looked in the wrong place afterward. First go back to the exact entry point where you triggered the generation: the group channel, your DM with the bot, or the channel you commonly use for generating. Scrolling up by time is the most effective.

If you’ve recently switched accounts or authorization methods, it can also make your Midjourney history look discontinuous. It’s recommended to stick to one primary account for generating. When necessary, download important works locally or mark them as favorites in time—so even if chat history gets pushed down, it won’t affect your ability to retrieve your Midjourney works.

Blocked content warning appears: Don’t fight it—rewriting the description is faster

Most Midjourney blocks are related to “sensitive personal traits, violence, adult content, or impersonation of specific people/brands.” The system will directly refuse to generate or ask you to adjust. The approach is to shift the description from “a specific person/identifiable subject” to “style and elements”—for example, use “cinematic lighting, documentary lens, vintage film texture” to replace overly pointed descriptions.

If you’re only doing composition practice, you can first have Midjourney generate a generic scene, then gradually add details in later iterations—this is less likely to trigger blocks. If you keep getting blocked repeatedly, the easiest approach is to delete potentially risky keywords, let Midjourney successfully generate one version first, and then slowly add back the necessary information.

No permission prompt or bot unavailable: Usually an environment/permissions issue

If Midjourney suddenly tells you that you can’t use it, common reasons include the channel/server you’re in not allowing commands, or the bot not being added properly. First confirm you’re entering commands in a channel where Midjourney is allowed, and check whether you have permission to speak in that channel.

If it’s a newly joined server or a newly created channel, an admin may need to add the Midjourney bot and grant it read/write permissions. When dealing with this kind of issue, don’t rush to repeatedly retry the same sentence; first verify these three items: channel permissions, whether the bot is online, and whether you’ve been muted. Usually that will restore Midjourney to normal generation.