When using Midjourney, if it suddenly stops generating images, commands don’t respond, or you get a “no permission” message, it’s usually not that “the system is broken,” but rather an issue with the Discord connection, channel permissions, or asset links. Below is a set of Midjourney troubleshooting steps organized by the most common error scenarios to help you pinpoint the problem quickly.
Commands not responding: Interaction failed / App not responding
If, after typing /imagine in Discord, you see “Interaction failed” or it looks like nothing happens at all, don’t rush to resend. First refresh the Discord client (or force-refresh the web version), then confirm that the Midjourney bot is still in the channel where you sent the command and is online.
If it only fails in a particular server, try an official channel or another channel you know works. This quickly tells you whether it’s a “server permissions issue” or a “connection issue on your side.” Also, network instability can cause Discord interactions to time out—once your connection is stable, sending the command again often resolves it.
Queue stuck: Job queued / Waiting to start keeps hanging
If Midjourney shows “Job queued” or “Waiting to start” and stays stuck for a long time, it’s usually because the queue is crowded or your request wasn’t delivered properly. First send a simple prompt in the same channel to test (for example, just subject + style) and see whether it enters the queue normally.
If all tasks are stuck, reduce the number of jobs you submit at the same time, and check whether you repeatedly clicked generate in a short period, causing a backlog. Midjourney occasionally has brief congestion; switching channels or trying again later is often more effective than repeatedly spamming clicks.


