Midjourney Troubleshooting: Fixing Unresponsive Buttons, Missing Jobs, and Upscale Failures

The most annoying part of making images isn’t the queue—it’s when buttons do nothing, upscales fail, or a job seems to “vanish” and you can’t find it. This article covers only the three most common Midjourney troubleshooting cases: broken interactive buttons, missing job history, and Upscale/Variation errors. Follow the steps below and you can usually identify the cause on the spot in Discord and recover the job.

Buttons do nothing: Check interaction permissions and channel type first

When Midjourney troubleshooting and U1/U2/V1/V2 or the 🔄 reroll doesn’t work, first check whether the channel you’re in allows “Use Application Commands/Interactions.” On a private server, make sure the bot has permissions such as “Send Messages,” “Embed Links,” “Attach Files,” “Read Message History,” and “Use Application Commands”; otherwise, buttons often look like they were clicked but won’t execute.

If it works on the official server but not in your own channel, it’s almost certainly a permissions or channel rule issue. Kicking the bot and inviting it again, or testing in a brand-new channel, is the fastest Midjourney troubleshooting method.

Upscale fails or spins forever: Check queue status and command parameters

If an Upscale gets stuck, first see whether the channel shows any system prompts such as “job rejected / queue busy / interaction failed.” Midjourney troubleshooting recommends sending “/imagine” or “/info” again in the same channel; if even basic commands don’t respond, it’s likely Discord’s interaction system is acting up or the bot’s permissions are restricted.

Also don’t overlook parameter conflicts: certain custom settings can make the output size or mode incompatible, which can easily cause upscales to fail. Temporarily switching back to the default mode via “/settings” and trying again is a very practical Midjourney troubleshooting tip.

The job is “gone” and you can’t find it: Recover it with /show using the Job ID

Not seeing your past images doesn’t necessarily mean generation failed—more often you switched channels/DMs/servers, or the Discord message got pushed out of view. During Midjourney troubleshooting, open “/info” to check recent job records, then find the Job ID in your message history and use “/show <JobID>” to pull the image back up.

If you’re logged in on multiple devices, also confirm you didn’t switch to the wrong Discord account. Account switching that makes you “think the images are gone” is one of the most common but easiest-to-miss Midjourney troubleshooting causes.

Interaction failures and abnormal image loading: Identify network and media delivery issues first

When you see “This interaction failed” or image thumbnails are blank, Midjourney troubleshooting shouldn’t focus only on the bot—the Discord media delivery path is just as critical. Try “Open in browser,” switch networks, disable any proxies/extensions that block media, then refresh the client.

If the desktop app is acting up, clear the Discord cache or use the web version to check whether the issue reproduces: if the web version works but the client doesn’t, it’s usually a local cache or client state problem. After these steps, most Midjourney troubleshooting quickly converges on a clear cause.