When using Midjourney to generate images, the most frustrating thing is that you send the prompt but get no result back, or it directly says it failed. Below, in the order of “most common and easiest to self-check,” we’ll break down and troubleshoot the causes of Midjourney generation failures. If you follow the steps once, you can basically pinpoint whether the issue is permissions, the queue, asset links, or content filtering.
First, check the channel and permissions: can the bot work properly?
Midjourney runs in Discord, and the most common pitfall is “you’re sending commands, but the bot doesn’t have permission here.” Confirm that you’re entering /imagine in an available channel, and that the channel allows Midjourney to send messages and upload files. If you’re using Midjourney in a private channel or a newly created server, check whether you’ve added the bot to the server and whether it has permission to speak/post and attach files.
If you can see the Midjourney bot online but it doesn’t respond at all, first switch to an official public channel or a channel you know works and do a quick comparison test. This comparison can quickly rule out issues caused by “this channel’s permissions/rules.”
Commands won’t send: Unknown Interaction and failed message sending
If you encounter “Unknown Interaction,” it’s usually because you clicked a button too slowly, the Discord interaction timed out, or network jitter caused the callback to fail. The fix is simple: resend /imagine; don’t reuse buttons on an old message. Also, try to operate in the desktop Discord client, which is more stable. If it happens frequently, log out of Discord and log back in—many times that restores it immediately.
If it’s “Failed to send,” first check whether the top-left of Discord shows reconnecting or latency spiking. Midjourney itself hasn’t changed, but when the Discord connection is unstable, the command can get “dropped” on the way, like packet loss.
Jobs stuck in the queue: what to do if it stays on Queued/Processing
If Midjourney shows that it’s queued for a long time, it doesn’t necessarily mean there’s something wrong with your account; more often, overall load is high at that time. First, submit fewer jobs at once—wait until the previous one enters generation before sending the next. Also avoid repeatedly clicking “reroll/variations” on the same job, which can easily make the queue pile up. You can also switch to a less crowded channel and send it again, to see whether it enters processing faster.


