In the Midjourney web editor, the most common pitfalls aren’t the prompts, but “can’t click, can’t select, can’t submit.” This article focuses only on Midjourney troubleshooting: when the submit button turns gray, the mask/selection doesn’t work, or a job gets stuck on submitting or generating, follow the steps to quickly pinpoint whether the issue is your network, browser, or the asset itself.
Start with two quick checks: narrow the problem down to “account / network / browser”
When troubleshooting Midjourney, first open the editor in an incognito window and log in again to rule out cache and extension interference. Then switch networks once (Wi‑Fi/mobile hotspot) or switch browser engines (Chrome/Edge) to see whether the issue follows the environment. If it works immediately after changing environments, the troubleshooting direction is basically browser cache, script blocking, or an unstable network.
Submit button grayed out: usually the asset or permissions failed validation
A gray submit button usually doesn’t mean “the system is broken”—it means the editor hasn’t passed validation yet. In Midjourney troubleshooting, first check whether any required step is incomplete, such as not selecting an image to edit, not confirming the changes, or having conflicting parameters. Next, check the asset: an oversized upload, an uncommon format, or a file that’s still uploading can all keep the button gray. Finally, confirm your account actually has available generation permissions; when permissions haven’t taken effect, the page may also present as an unusable button—this is the most easily overlooked troubleshooting point.
Mask/selection not working: first rule out zoom level and script blocking
If you can’t draw a selection or the mask brush doesn’t respond, in Midjourney troubleshooting first reset the canvas zoom to a suitable level and make sure your cursor is truly on the canvas layer rather than the page scrolling layer. Then disable ad blockers, privacy anti-tracking, and script-blocking extensions (including some “reader mode/immersive translation” tools); these extensions rewrite front-end events and most easily break the selection tools. If you’re using a trackpad or touchscreen, try switching to a mouse and refreshing the page—also a common troubleshooting shortcut.
Stuck on “Submitting” or not generating: check the queue, rate limits, and the status page
If a job keeps spinning without producing results, Midjourney troubleshooting suggests retrying only a small number of times to avoid stacking requests by clicking repeatedly, which can trigger rate limiting. Open the site status page (if there are announcements) or check for server-side congestion messages; when the server is congested, nothing you do locally will make it faster. If only you are stuck, prioritize clearing site cache, hard-refreshing the page, and checking whether your network is unfriendly to long-lived connections (common with corporate proxies and public networks). This is the most effective troubleshooting combination for “stuck submitting / stuck generating.”
If it still doesn’t work: capture evidence in a “reproducible” way before reporting
If you’ve completed the basic Midjourney troubleshooting steps and can still reproduce the issue consistently, record three things: the exact action path (which buttons you clicked), the asset type/source before the issue occurred, and your browser and network environment. Screenshots or screen recordings should include on-page prompts and loading states, so officials or the community can judge whether it’s a front-end error, an asset validation failure, or an abnormal server queue. Reporting with reproducible materials often resolves the “hard cases” in troubleshooting faster than endlessly refreshing.
