Midjourney FAQ: Fixing No Response from the Bot, Invalid Commands, and Stuck Queues

When using Midjourney, the most annoying part is often not the image quality, but “the bot doesn’t reply,” “the command errors out,” or “it stays queued forever.” This article breaks down the most common issues by scenario and gives a practical, step-by-step checklist so you can quickly get back to generating images normally.

Bot not responding: First confirm the channel, permissions, and bot status

Midjourney works in Discord. The most common cause is sending it in the wrong place: enter the slash command (/imagine) in a channel where the bot is allowed; some server channels disable bot messages. Next, check whether the Midjourney bot is online. If you can’t see the bot in the server, you may need to re-invite it, or an admin may not have granted it permission to speak.

If it only doesn’t respond for you, try logging out of Discord and back in, or test again in Discord’s web version. If there’s a widespread lack of responses, it’s usually congestion on Midjourney’s side or a Discord hiccup—wait a few minutes and then send the same command again, and avoid rapid repeated clicks that can slow things down further.

Invalid command / parameter errors: Use slash commands and avoid “special character traps”

Midjourney now primarily uses slash commands. Prefer triggering the input box with /imagine, then paste your prompt—this reduces format-parsing issues. Parameters must use English double hyphens (e.g., --ar 16:9). Chinese dashes, full-width spaces, or fancy quotation marks can all cause Midjourney to treat parameters as invalid.

If it says a parameter isn’t supported, it’s usually a model/version mismatch or a spelling mistake; the fastest approach is to remove parameters one by one to test. If you see prompts like “content is restricted,” switch to more neutral wording and avoid directly copying an entire prompt that contains sensitive terms.

Stuck on Queued: Check mode and concurrency, then decide if the system is congested

Queues are common during peak hours or when you have multiple jobs running at once; stop extra jobs first, then send a very short test prompt to confirm the pipeline works. If you’re in Relax mode, longer queues are normal; if you need faster results, switch to Fast (some accounts are limited by available time or queue rules).

Also, repeatedly resending the same job in Discord doesn’t necessarily make it faster, and can actually make the queue messier. A more reliable approach is to wait 1–3 minutes to see whether the job continues to move forward, and check the job list on the Midjourney website to see whether there’s real progress.

Prompts asking for a subscription / insufficient permissions: First verify you’re logged into the same Discord account

If you see “valid subscription required” or an insufficient-permissions message, don’t rush to pay again. First confirm that the Discord account you’re logged into on the Midjourney website is the same one you’re using to send commands in Discord. Many people switch between phone and computer or between multiple Discord alts, causing Midjourney to recognize the “non-subscribed” account.

The correct approach: log out on midjourney.com, then log back in with the intended Discord account; return to Discord and test /imagine with that same account. If it still shows an error, then check whether the subscription has expired, was refunded, or the payment didn’t complete—these statuses usually sync to the account page on the website.