Midjourney FAQ: Fixing Discord Authorization Issues and an Unresponsive Bot

When using Midjourney, the most common sticking points aren’t prompts, but Discord authorization, the bot not replying, or incorrect channel permissions. Below, these high-frequency issues are organized into a ready-to-follow FAQ in the format “symptom — cause — fix.” If you run into a similar situation, checking in order usually restores Midjourney image generation quickly.

1. Midjourney authorization failed: the website and Discord don’t match

If Midjourney prompts you to log in or repeatedly bounces you back to the authorization page, in most cases the Discord account logged into your browser doesn’t match the account you normally use. First, log out of Discord Web in your browser, then log back in with the correct account and return to Midjourney’s Account/authorization page to try again. If it still loops, clear the site’s cookies or use an incognito window; then re-authorizing is usually cleaner.

Also, if your Discord account hasn’t completed email verification or is being asked for two-factor verification, Midjourney may be unable to finish linking. Go to Discord settings and complete email verification and phone verification (if required), then return to Midjourney and authorize again.

2. Bot not responding: message sent but Midjourney doesn’t react

If you enter a command in a channel and Midjourney does nothing, first confirm you’re using a slash command (i.e., a command starting with “/”), not plain text. If you can’t find any Midjourney-related items in the slash-command list, it’s usually because the bot isn’t in that server/channel, or you don’t have permission to use application commands in that channel.

It’s also worth checking in Discord whether you’ve muted or blocked the Midjourney bot, or disabled permissions related to “application commands.” Ask another member in the same server to test; if it doesn’t respond for them either, it’s more likely a channel-permission issue or that the bot wasn’t added correctly.

3. You can see the bot but can’t use it: channel permissions and role settings

Midjourney needs permissions in the channel such as “View Channel” and “Send Messages/Use Application Commands.” Missing even one can show up as “can see it but can’t use it.” If you’re generating images in a private channel, remember to explicitly add the Midjourney bot (or its role) to that channel’s permission list. Admins can verify items one by one via “Channel Settings → Permissions,” then re-enter the channel and try the command again.

Some servers enable stricter command restrictions, making Midjourney usable only in designated channels. The easiest approach is to first test whether Midjourney works in the public default channel, then copy that permission configuration to your private image-generation channel.

4. Commands send but image generation fails: queueing, content restrictions, and status checks

If Midjourney shows the request was received but doesn’t generate an image for a long time, first check whether it’s simply queue delay: wait times can be noticeably longer during peak hours. If it returns a content restriction or safety warning, it’s usually because the prompt involves sensitive topics—try again with a more neutral, more specific description. If you suspect an account-status issue, go to Midjourney’s Account page to confirm you’re logged into the correct account and whether there are any prompts or terms pop-ups that need confirmation.

If it’s still abnormal after the above steps, try switching both network and browser once, and create a clean test channel in Discord to verify whether Midjourney has recovered. This quickly helps determine whether it’s a local environment issue or something caused by channel/permission configuration that makes Midjourney unusable.