Midjourney Command Not Working: Troubleshooting Discord Permissions, Channel Settings, and Bot Status

If Midjourney suddenly stops working, in most cases it’s not because the “model is broken,” but because of Discord-side permissions, the channel type, or the bot being offline. Below is a Midjourney troubleshooting checklist ordered from fastest to slowest, focusing on common sticking points such as “/imagine not responding,” interaction failures, and insufficient permissions.

Start with two quick checks: bot online status and service status

When troubleshooting Midjourney errors, first check whether the Midjourney Bot is online in the channel member list; if the bot isn’t in your server, commands obviously won’t work. Next, Discord’s occasional instability can cause interactions to time out directly, and you’ll see “Interaction Failed/This interaction failed.”

If you use Midjourney across multiple servers, return first to the channel you know works and run a quick test to avoid misjudging a “channel configuration issue” as an “account issue.” This step is the fastest way to narrow the troubleshooting scope to “bot/platform” versus “local configuration.”

/imagine not responding: it’s usually the channel or permissions not set correctly

The most common issue in Midjourney troubleshooting is that you can type the command, but no options pop up, or nothing happens after you submit it: first confirm you’re in a “text channel,” not an announcement channel, forum, or a channel where you’re restricted from speaking. Then check your role permissions—at minimum, you must be allowed to “Use Application Commands” and “Send Messages.”

If admins have configured granular permissions, Midjourney troubleshooting also needs you to enable “View Channel,” “Read Message History,” “Embed Links,” and “Attach Files.” If “Embed Links/Attach Files” is missing, it often shows up as being able to queue jobs but not see images or the results can’t be returned.

Common error reference: Missing Permissions and Unknown interaction

If you see “Missing Permissions,” there’s basically no need to guess—the Discord permission chain isn’t correctly set up. After enabling the permissions item by item as above, rerun the Midjourney troubleshooting test. If it says “Unknown interaction,” it’s usually because you clicked a button too slowly, the network hiccupped, or Discord latency caused the interaction to expire—just resend the command.

There’s also a case where it “seems like there’s no error but no images are generated”: you posted in a channel where the bot is disabled, or admins only allow application commands in specific channels. During Midjourney troubleshooting, move the exact same command to another open text channel; it’s often an immediate way to confirm the conclusion.

The bot is present but still not working: reload commands and reinvite

After you confirm permissions are fine, there are two things you can do in Midjourney troubleshooting: ask an admin to re-authorize application commands in the server (sometimes Discord caching causes the command list to get out of sync), and check whether the bot was mistakenly kicked or restricted to being visible only in certain channels. If the bot is absent, reinviting the Midjourney Bot to the server will usually restore functionality directly.

Final reminder: if the system clearly indicates you need a subscription or you’re out of credits, this isn’t “commands not working,” but an account-status limitation. The key to Midjourney troubleshooting is to first fully rule out Discord-side “permissions, channel, and bot online status,” then handle any account prompts—this is the most efficient approach.