What to Include in a Midjourney Bug Report
A well-structured bug report dramatically increases your chances of a fast resolution. Include every item in this list.
Required Information
1. Exact error message Copy-paste the complete error text. Do not paraphrase. "An error occurred" is not useful; the exact error code or message is.
2. Steps to reproduce Write out exactly what you did, step by step, before the error appeared. Example:
- Open Discord and go to the Midjourney server
- Type /imagine in the #newbies channel
- Enter prompt: [exact prompt here]
- Press Enter
- Error appears: [exact error message]
3. Full prompt used Include the complete prompt, including any parameters like --ar, --v, --q, or --no flags.
4. Your plan tier Specify: Basic ($10/mo), Standard ($30/mo), Pro ($60/mo), or Mega ($120/mo). Some bugs only affect specific plan tiers.
5. Access method Specify whether you are using:
- Discord bot (and which server/channel)
- Midjourney web interface at midjourney.com
- Fast mode or Relax mode at time of error
6. Timestamps Note the exact time and timezone when the error occurred. This helps Midjourney match your report to server logs.
7. Environment details
- Browser and version (if using the web interface)
- Operating system and version
- Discord app version (if using Discord)
8. Screenshot or screen recording Visual evidence of the bug is far more useful than a text description alone.
Step-by-Step: How to Submit the Report
1. Check for Active Incidents First
Visit status.midjourney.com before reporting. If there is an active incident, your bug is known. Add a comment to the existing incident thread rather than filing a new report.
2. Reproduce the Bug
Before reporting, try to reproduce the bug at least twice. A bug you can consistently reproduce is much easier to fix than one that appeared once.
Try the same action:
- On a different device or browser
- On a different network (mobile hotspot vs. Wi-Fi)
- With a different but similar prompt
This tells you whether the bug is local or global and provides essential context.
3. Choose the Right Report Channel
For widespread bugs (generation failures, bot outages): → Report in the Midjourney Discord server's dedicated bug or feedback channel
For account-specific bugs (billing errors, missing images, plan issues): → Use the support form at docs.midjourney.com
For potential content policy false positives (prompts blocked in error): → Use the support form and reference the specific prompt and why it should be within policy
4. Write the Report
Use this template:
Bug: [One sentence description]
Plan: [Basic/Standard/Pro/Mega]
Interface: [Discord bot / Web interface]
Time of occurrence: [Date and time in UTC]
Steps to reproduce:
1. [Step 1]
2. [Step 2]
3. [Step 3]
Error message: [Exact text]
Full prompt used: [Complete prompt with parameters]
Environment: [Browser + OS or Discord app version]
Frequency: [Always / Intermittent / Happened once]
[Attach screenshot or screen recording]
5. Follow Up Appropriately
If reporting on Discord, monitor the thread for replies. If reporting via the support form, check the email address associated with your Midjourney account for a response. Do not file duplicate reports for the same issue — this slows down the support queue.
Why This Happens
Bugs in AI image generation systems like Midjourney come from a wide range of sources: server-side queue failures, model inference errors, Discord API integration issues, browser rendering problems, or billing system edge cases. Without specific reproduction information, Midjourney's engineering team cannot distinguish between a one-off glitch and a systemic failure. Detailed reports enable faster diagnosis and fix deployment.
Common Mistakes to Avoid
- Reporting a known incident as a new bug — Check status.midjourney.com first.
- Providing vague error descriptions — Copy-paste the exact error text; do not summarize it.
- Forgetting to include your plan tier — Some bugs only affect specific subscription levels.
- Not testing on a second device or network — This single test often tells you whether the bug is local or server-side.
- Filing multiple reports for the same issue — One clear, detailed report is more effective than three vague ones.
Related Issues
- Midjourney job failed / image not generating
- Midjourney interaction failed / bot not responding
- Midjourney stuck in queue for a long time
- Midjourney too many requests
Q: Is there a bug tracker I can follow for Midjourney issues? Midjourney does not publish a public bug tracker, but the official Discord server's #announcements and #status channels are the closest equivalent. Significant bugs affecting many users are usually acknowledged there within hours. The status page at status.midjourney.com tracks service-level incidents. For feature requests and minor bugs, the #feedback channel in the official Discord server is where the community and Midjourney team discuss known issues.
Q: What plan tier should I include in my bug report? Always specify your exact plan: Basic ($10/mo), Standard ($30/mo), Pro ($60/mo), or Mega ($120/mo). Some bugs only reproduce on specific tiers — for example, a bug in Stealth Mode generation only affects Pro and Mega users, and Relax mode bugs only affect Standard and above. Including your plan tier immediately narrows the scope of the investigation and prevents the support team from asking follow-up questions.
Additional FAQ
Q: How do I know if the problem is on my end or the platform's side? Check the platform's official status page first — most services maintain a public status page that shows current incidents and outages. If no incident is posted and the problem only affects your account (not reported widely on Reddit or Twitter), it is likely a local issue. Testing in incognito mode and on a different network also helps isolate whether the problem is browser-specific, network-specific, or account-specific.