Step-by-Step Fix
1. Stop All New Submissions Immediately
When you see "too many requests," treat it as a hard stop signal:
- Stop typing or submitting
/imaginecommands - Do not click any pending retry buttons
- Close any extra Discord windows you have open for Midjourney
- Pause for at least 60 seconds
This step alone resolves the issue for most users.
2. Check Your Current Job Queue
Run /info to understand your current state:
/info
This shows:
- How many jobs are currently active or queued
- Your remaining Fast GPU hours
- Your subscription plan and tier
If you have 3 active jobs and a 0 GPU hours balance, you have two separate issues: a rate limit and an exhausted Fast hour allocation.
3. Wait for Active Jobs to Complete
Each Midjourney generation job in Fast mode takes approximately 30 to 90 seconds to complete. Watch the Discord channel for job completion messages (the 4-image grid appearing). Once you see results, one of your concurrent slots has freed up.
- Do not submit new jobs until you see results from pending ones
- Use the U (upscale) and V (variation) buttons on your existing results rather than starting new generation jobs
4. Switch to Relax Mode
If you are on Standard, Pro, or Mega plan, switch to Relax mode:
/relax
In Relax mode:
- No strict concurrent job cap applies
- Jobs take 2 to 10 minutes depending on server load
- Fast GPU hours are not consumed
- You can continue working while Fast mode limits clear
Switch back to Fast mode anytime with /fast.
5. Space Out Future Submissions
To prevent recurring too many requests errors:
- Wait for the image grid to appear before submitting your next prompt
- Aim for no more than 2 active jobs at a time as a buffer below the 3-job limit
- Use
/imaginewith multiple descriptors in one prompt rather than submitting separate prompts for each variation you want to test
6. Upgrade for Higher Concurrency
If your workflow consistently requires more than 3 parallel jobs:
- Pro ($60/mo): 12 concurrent Fast jobs, 30 Fast GPU hours
- Mega ($120/mo): 12 concurrent Fast jobs, 60 Fast GPU hours
At $60/month, Pro roughly quadruples your concurrent generation capacity.
Why This Happens
Midjourney's image generation infrastructure is a shared GPU cluster. Each active generation job holds a GPU slot for the duration of rendering. The "too many requests" error is the queue manager's way of enforcing per-account fairness — when your 3 slots are occupied, additional requests are rejected until a slot frees up. This is by design and affects all users equally regardless of plan tier, except Pro and Mega users who have a 12-slot allowance.
Common Mistakes to Avoid
- Treating it like a temporary outage — "too many requests" is not a server problem; Midjourney is working fine, you simply have too many jobs queued from your account
- Opening multiple Discord accounts to bypass the limit — this violates Midjourney's terms of service and can result in permanent account bans
- Not knowing about Relax mode — tens of thousands of Midjourney users are unaware that Relax mode exists; on Standard and above, it is a free, always-available workaround for concurrency issues
- Using third-party batch tools without throttling — tools that submit 10 or 20 prompts simultaneously will always trigger too many requests errors; configure batch tools to submit jobs one at a time with a delay between submissions
- Upgrading before trying Relax mode — for most Standard users, switching to Relax mode fully resolves too many requests issues without requiring a plan upgrade
Related Issues
- Midjourney Rate Limit
- Midjourney Rate Limit Exceeded
- Midjourney Usage Limit
- Midjourney API Rate Limit
- Midjourney limit reached — what to do next
Why This Happens
Midjourney runs on shared GPU clusters where each generation job occupies a processing slot. The "too many requests" error is the system's real-time enforcement of per-account fairness limits — Basic and Standard plan users get 3 simultaneous Fast mode slots, while Pro and Mega users get up to 12. When all slots are occupied and you submit another job, the system rejects the new request rather than queuing it indefinitely. This prevents a single account from monopolizing GPU capacity at the expense of other users.
Common Mistakes to Avoid
- Treating the error like an outage — "Too many requests" means Midjourney is working normally; you specifically have too many concurrent jobs, not a platform failure.
- Opening multiple Discord accounts to bypass the limit — This violates Midjourney's Terms of Service and can result in permanent bans on all associated accounts.
- Not knowing about Relax mode — Many Standard plan users are unaware that unlimited Relax mode is included. Switching to /relax immediately removes the concurrency pressure without any upgrade needed.
- Using batch automation tools without throttling — Tools that submit multiple prompts simultaneously will always trigger "too many requests." Configure batch tools to submit jobs sequentially with a delay of at least 30 seconds between submissions.
- Upgrading before trying Relax mode — For the majority of Standard users, switching to Relax mode completely resolves concurrent job issues without spending $30 more per month on Pro.
Q: If I am on the Basic plan, what do I do when I get 'too many requests'? On the Basic plan ($10/month), you have 3 concurrent Fast mode job slots and no Relax mode. If you hit "too many requests," your only options are to wait for your current jobs to complete before submitting new ones, or to upgrade to Standard ($30/month) to unlock Relax mode. On the Basic plan, submitting jobs one at a time and waiting for each grid result before sending the next prompt is the most reliable way to avoid the error.
Q: How do I know if 'too many requests' is about concurrent jobs or monthly limits? Use /info in Discord to distinguish between the two. If your response shows Fast hours remaining greater than zero but jobs queued or running at or above 3, the issue is concurrent job limits — you are not out of monthly allocation, just over the per-session concurrency cap. If /info shows 0 fast hours remaining, you have exhausted your monthly allocation — the fix is Relax mode or purchasing additional hours, not waiting 60 seconds.
Additional FAQ
Q: How do usage limits actually reset — daily or rolling? Most AI platforms use either a fixed daily reset (e.g., at midnight UTC) or a rolling window (e.g., your oldest message from 3 hours ago expires and frees up a slot). Rolling windows are more common for message and request limits because they distribute server load more evenly. Check the platform's help documentation for the exact mechanism — the support page for your specific limit usually specifies the reset type and time zone.
Related Articles
- Midjourney not generating images
- Midjourney login not working
- Midjourney payment failed
- Midjourney rate limit exceeded
Additional FAQ
Q: How do usage limits actually reset — daily or rolling? Most AI platforms use either a fixed daily reset (e.g., at midnight UTC) or a rolling window (e.g., your oldest message from 3 hours ago expires and frees up a slot). Rolling windows are more common for message and request limits because they distribute server load more evenly. Check the platform's help documentation for the exact mechanism — the support page for your specific limit usually specifies the reset type and time zone.