A stuck Midjourney queue is one of the most frustrating experiences on the platform: you submit a prompt, Discord shows 'Waiting to start', and nothing happens. The cause is almost always one of four things: Midjourney server capacity, your Fast mode GPU hours being exhausted, the Midjourney Discord bot being offline, or a job that entered a failed state silently. Here's how to quickly identify which and fix it.
'Waiting to start' message under your prompt that never progresses to a percentage
Job submits successfully but no progress bar appears after 60+ seconds
Queue shows position (e.g., 'Queue Position: 4') but count never decreases
'Fast mode' indicator in /info shows 0 remaining but you're trying to generate
Midjourney bot in Discord shows as offline or isn't responding to commands
/imagine command returns no response from the bot at all
Previous jobs completed but new jobs all get stuck at the same point
Job appears to complete (100%) but no image appears in the channel
Midjourney's subscription plans include a fixed number of 'Fast mode' GPU hours per month — the compute quota that lets your jobs render quickly. Basic plan: 3.3 hours/month. Standard: 15 hours/month. Pro: 30 hours. When these hours run out mid-month, jobs either queue in 'Relax mode' (slow, often 10-20 minute wait) or appear stuck if you're on Basic plan which doesn't include Relax mode. Check /info to see your remaining Fast hours.
Midjourney's GPU cluster can get overwhelmed during peak times (US afternoons/evenings), after viral moments on social media, or during the launch of new features or models. During these periods, even queued jobs may wait 5-15 minutes before starting. True outages (all jobs stuck, bot offline) are rarer but happen several times per year.
Midjourney's service runs via Discord bots. When Midjourney deploys updates or their infrastructure restarts, the bot goes offline briefly. Jobs submitted during the offline window may queue without processing, or appear stuck after the bot comes back. Bot status is visible in Discord: it shows as gray (offline) vs green (online) in the server member list.
Occasionally a job submits, appears to queue normally, and Midjourney's system registers it as in-progress — but the actual render task fails silently. The 'Waiting to start' counter shows but the job never progresses. This can happen after connection drops, unusual prompt content, or very long aspect ratios or parameters that cause backend errors.
If your Midjourney subscription payment fails, your account may be paused. Jobs still queue (the bot accepts them) but don't generate because your account lacks active compute access. This can look identical to server-side queue issues — no obvious error message, just perpetual 'Waiting to start'.
Midjourney's bot only processes jobs in authorized channels. If you use /imagine in a Discord server channel where Midjourney bot hasn't been added, or in a DM where it's not configured, the command may appear to accept but never generate. The bot needs the right permissions in the channel to process jobs.
When to try: First — gives you the most diagnostic information instantly
In any Midjourney channel or your Midjourney bot DM, type /info and send. The response shows: Fast hours remaining this month, your current mode (Fast/Relax/Turbo), subscription status, and lifetime usage. If Fast hours show 0.00/0.00 remaining and you're on Basic plan, that's your problem — you've hit your monthly limit. If subscription shows 'paused' or 'expired', payment failed.
When to try: After confirming Fast hours are at 0 in /info
Type /relax and send in a Midjourney channel. This switches you from Fast mode to Relax mode, which uses community GPU time at no cost to your monthly hours. Relax mode jobs typically take 3-20 minutes depending on queue depth, versus 30-90 seconds for Fast mode. Standard and Pro plans include unlimited Relax mode. Basic plan does not — you'll need to wait for next month or upgrade. To switch back to Fast mode: type /fast.
When to try: If /info works but new jobs still won't start
In any Discord server that has the Midjourney bot, look at the member list on the right side — find 'Midjourney Bot' and check its status dot. Green = online, yellow = idle, gray = offline. If offline, Midjourney is updating or having an incident. Wait 5-15 minutes and try again. You can also go to status.midjourney.com for official status. Jobs submitted during offline windows may need to be resubmitted after the bot comes back.
When to try: When a specific job has been at 'Waiting to start' for more than 5 minutes
React to the stuck 'Waiting to start' message with the ❌ emoji, or click the X button that appears under the job. This cancels the stuck queue entry. Wait 30 seconds, then resubmit the same prompt. If the job was stuck due to a silent backend error, the resubmitted job usually processes normally. If all resubmitted jobs also get stuck, the issue is account-wide or server-wide, not prompt-specific.
When to try: To isolate whether the issue is channel-specific
Try generating in Midjourney's official Discord server (discord.gg/midjourney) in the #general-image-generation channels — this confirms whether the issue is with a specific server/channel rather than Midjourney globally. Alternatively, use Midjourney's web app at midjourney.com (launched 2024) which processes jobs independently of Discord. If the web app works but Discord doesn't, the issue is channel/server permissions.
When to try: If /info shows subscription issues or your account seems paused
Go to midjourney.com → sign in → click your account/profile → Manage Subscription. Check for payment failure notifications or 'Paused' status. If payment failed, update your payment method and reactivate. Midjourney will notify via Discord DM when payment fails, so check your DMs from the Midjourney bot. After resolving billing, it may take 5-10 minutes for your account to reactivate before jobs start processing.
When to try: When Fast mode jobs are extremely slow (not stuck, just slow) during peak hours
If you have Fast hours remaining but jobs are still slow (2-5 minute waits), type /turbo to switch to Turbo mode. Turbo mode costs 4x your Fast hours but jumps the queue ahead of standard Fast jobs. During peak-demand periods, Turbo mode can get your jobs generating in seconds while standard Fast jobs queue for minutes. Use /fast to revert when your urgent work is done.
Run /info at the start of a heavy generation session to check your remaining Fast hours before hitting limits mid-project
Enable Relax mode notifications in your settings so you get alerted before Fast hours run out
Follow @midjourney on Twitter and join Midjourney's official Discord for advance notice of planned maintenance
For large batch projects, spread generation across multiple days to stay within monthly Fast hour limits
Use the Midjourney web app (midjourney.com) as a backup — it has its own queue separate from Discord
Upgrade from Basic to Standard plan if you frequently exhaust Fast hours — Standard's 15 hours/month plus unlimited Relax covers most power users
Contact Midjourney support at midjourney.com/support or through the help channels in Midjourney's official Discord server if: (1) Your /info shows remaining Fast hours but jobs are consistently stuck for over 30 minutes, (2) A payment was charged but your subscription shows as paused, (3) You've been unable to generate for over 24 hours with no status page incident. For general queue slowness during peaks, support can't accelerate individual jobs — that's infrastructure capacity. Midjourney's Discord support community is often faster than formal support tickets for troubleshooting. Verified April 2026.
Three most common causes: (1) Fast mode GPU hours are at 0 — run /info to check; if exhausted, run /relax to switch to slower but unlimited Relax mode. (2) The Midjourney bot is offline for updates — check the bot's status dot in Discord's member list; gray means offline, wait 5-15 minutes. (3) The job entered a silent failure state — cancel it with ❌ and resubmit. If all three are fine and it's still stuck, Midjourney is likely experiencing high load; wait 10-20 minutes.
Type /info in any Midjourney channel or DM the Midjourney bot directly with /info. The response shows 'Fast Time Remaining' — your GPU hour quota for the current billing period. When this hits 0, jobs either queue in Relax mode (Standard/Pro plans) or stop generating (Basic plan). Fast hours reset on your monthly billing date, not calendar month end. The /info command also shows your subscription tier, lifetime image count, and current mode.
Relax mode uses shared community GPU capacity rather than dedicated Fast mode compute. Jobs queue behind other Relax users and render when capacity is available. As of April 2026, Relax mode wait times typically range from 2-20 minutes, though during peak usage (US evenings) it can be longer. Image quality is identical to Fast mode — only the wait time differs. Standard and Pro plans include unlimited Relax mode at no extra cost; Basic plan does not include Relax.
Check status.midjourney.com for official service status. For faster real-time confirmation, search 'Midjourney down' or 'Midjourney stuck' on Twitter/X — users post immediately when issues start. In Midjourney's official Discord, the #announcements channel posts maintenance windows and outage updates. Midjourney's Discord bot status (green/gray dot in server member list) is also a direct indicator of whether the service is accepting jobs.
When some jobs work but others get stuck, it's usually prompt-specific. Certain parameter combinations, very long aspect ratios (like --ar 1:10), extremely high --tile resolutions, or specific model versions can cause backend errors that register as stuck queues. Identify what's different about the stuck prompts versus working ones. Test by removing parameters one at a time. Very long or unusual prompts are common culprits — try simplifying the stuck prompt.
Yes. React to the stuck job message in Discord with the ❌ emoji, or click the cancel button that appears under a queued job. The job is cancelled immediately and any Fast hours it would have consumed are not charged (since rendering never started). After cancelling, wait 60 seconds before resubmitting. If the same prompt gets stuck again, the issue is either prompt-specific or account/server-wide rather than a one-off glitch.
Often yes, because the web app at midjourney.com processes jobs through a different queue than Discord. During Discord bot outages or specific channel issues, the web app often continues working normally. The web app has the same feature set as Discord-based generation and uses the same Fast/Relax hour budget from your account. If Discord is having issues, web app generation is the cleanest workaround.
Midjourney doesn't limit image count directly — limits are in GPU compute hours. As of April 2026: Basic plan ($10/mo) includes 3.33 Fast hours (~200 images at default settings); Standard ($30/mo) includes 15 Fast hours (~900 images) plus unlimited Relax mode; Pro ($60/mo) includes 30 Fast hours plus unlimited Relax mode; Mega ($120/mo) includes 60 Fast hours. Standard and above plans with unlimited Relax can generate several thousand images per month. Verified April 2026.