Midjourney FAQ: Role Permissions, Account Linking, and Missing Creations

When using Midjourney, the easiest places to get stuck are “subscription paid but permissions didn’t change,” “it stops working after switching Discord accounts,” and “can’t find the images I generated.” Below, these high-frequency issues are broken down by scenario—follow the checklist and you can usually pinpoint the cause.

Subscription successful but permissions not applied: first verify account linking

Midjourney subscription benefits are tied to the Discord account you authorized for login. The most common case is that you authorized Account A when paying, but you’re actually using Account B in Discord. Open the account page on the Midjourney website and confirm the displayed Discord username matches the one you’re currently logged into, then go back to Discord and use “/info” to see whether the subscription status has updated.

If everything matches but it still shows no permissions, log out on the website and re-authorize login with Discord, then refresh the Discord client or log in again. If it still doesn’t take effect, keep your payment proof and account email and submit a billing issue through the official support channels to avoid repeated trial and error.

Can’t see your work or the gallery is empty: don’t search only in channels

Many people think the images exist only in Discord channels, so when they switch channels they “disappear.” Midjourney creations sync to the web gallery (Gallery/Archive). You can trace back by date and job history on the website, which is usually faster than scrolling chat logs.

If you can’t see them on the web either, first check whether you’ve authorized a different Discord account; also confirm whether content filtering is enabled or channel messages are collapsed. In shared channels with multiple people, it’s recommended to use the job ID or locate the specific generation record directly on the web.

Prompt sent but no response: permissions and the command entry point matter most

Midjourney is primarily used in Discord via slash commands. If you send commands in a channel where bots aren’t allowed, it often looks like “it sent, but nothing came back.” First switch to a channel that allows bots, or add the Midjourney Bot to a private server you created and try again.

Also make sure you’re entering slash commands like “/imagine,” not plain text messages; some clients require waiting for the command list to finish loading. If only one server is unresponsive, it’s likely that server’s permission settings are restricting the bot.

Can’t DM the bot: usually blocked by Discord privacy settings

Generating via DM with Midjourney is cleaner, but many people can’t send messages after clicking the bot’s avatar. Go to that Discord server’s privacy settings and allow “Direct Messages from server members,” then try initiating a DM with the Midjourney Bot again.

If it still doesn’t work, using your own private server is the most reliable approach: invite the Midjourney Bot into your own server and generate/manage jobs in a dedicated channel, where permissions and records are clearer.

Images keep queueing or load slowly: first confirm mode and network

Midjourney queue time is affected by mode and resource availability; Fast and Relax feel different, and your waiting strategy should change accordingly after switching. If the image preview keeps spinning or won’t open, Discord image-link loading may be unstable—try opening the original image on the Midjourney web side first, or retry after changing networks.

When you need to quickly pinpoint the issue, it’s recommended to do two things at the same time: use “/info” to confirm the current job and mode status, and check on the web whether the job has finished generating. This helps distinguish between “it didn’t generate” and “it generated but didn’t load on your side.”