Midjourney Troubleshooting Guide: Stuck in the Image Queue, Unresponsive Commands, and Permission Issues

When using Midjourney in Discord to generate images, the most common headache isn’t prompts—it’s “no response, stuck in queue, generation failed.” This article focuses only on Midjourney troubleshooting: from channel permissions and bot status to network issues and rate limits, helping you pinpoint the problem step by step and quickly resume generating images.

First, confirm whether the Midjourney bot is “present and available”

Search for “Midjourney Bot” in the member list of the current server to confirm it’s online and actually in this server. If you can’t find it, it’s most likely that the bot wasn’t invited or was kicked out—you’ll need to invite it again and authorize it to the target server.

Also check the type of channel where you’re sending commands: test once in a newly created regular text channel first, to avoid forum channels, announcement channels, or restricted channels causing Midjourney not to respond. Midjourney is very sensitive to permissions—the “cleaner” the channel, the easier it is to troubleshoot.

Commands sent but no response: Unknown interaction and This interaction failed

If you see “Unknown interaction / This interaction failed,” don’t repeatedly spam-click buttons. It’s usually a Discord interaction timeout or the client freezing. The most effective approach is to refresh Discord (Ctrl+R on desktop), or log out and log back in, then test /imagine in a new channel.

If it only fails in one specific channel but works normally in another, it’s basically due to channel permissions or slow mode. Have an admin check whether that channel has disabled “Send Messages / Use Application Commands” for you, and confirm that Midjourney-related commands aren’t being blocked under some role permission.

Stuck in queue with no image: Job queued and You are being rate limited

If you see “Job queued” and it doesn’t move, first check whether you have too many tasks running at once or if it’s peak time. Pause some unfinished tasks in the queue (avoid running multiple /imagine jobs in parallel), wait a minute or two, then send a new Midjourney task—this is usually faster than repeatedly resending.

If you get “You are being rate limited,” you’ve hit rate limiting: sending too many commands in a short time or repeatedly clicking Upscale/Variation can trigger it. The correct response is to pause for a few minutes before continuing and slow down your pace; persistently spamming will only make Midjourney ignore you for longer.

Generation fails or images won’t send: Practical self-checks from network to client

Midjourney generation depends on Discord and the image CDN; when the network is unstable, it may show up as images not loading or buttons producing no response. First switch networks (toggle between Wi‑Fi and hotspot), or turn off proxies/accelerators and try again; if your corporate network blocks it, switching to mobile data often works immediately.

On the browser version, clear the site cache and disable extensions that might block scripts; on the desktop app, update to the latest version. Finally, do one very important thing: try /imagine in a DM with Midjourney Bot. If it works in DMs but not in the channel, the problem can almost certainly be pinned on server permissions or channel settings.