Known Issues
Current known issues, limitations, and workarounds. This page is updated as issues are identified and resolved.
Midjourney content filter false positives
Midjourney's content filter occasionally rejects benign prompts, especially those containing words that have dual meanings (e.g., "shoot", "blow"). The task will fail with no specific error message.
Workaround
Rephrase the prompt to avoid ambiguous terms. If a prompt consistently fails, try adding context words that clarify the intent.
CDN image URLs may take 5-10 seconds to become available
After a task completes, the image URLs returned point to Midjourney's CDN. In rare cases, these URLs may return a 404 for a few seconds while the CDN propagates.
Workaround
If you get a 404 when downloading an image, retry after 5-10 seconds. This is a CDN propagation delay, not a permanent failure.
Upscale 2x/4x with image_url may have quality limitations
When using /upscale-2x-4x with an arbitrary image_url (not from a JourneyAPI task), the upscale quality depends on the input image quality and format. Very small or heavily compressed images may not upscale well.
Workaround
Use the highest quality source image available. PNG is preferred over JPEG for upscaling.
Blend requires publicly accessible image URLs
The /blend endpoint downloads images server-side. If your image URLs require authentication, cookies, or are behind a CDN with geographic restrictions, the download may fail silently.
Workaround
Ensure image URLs are publicly accessible with no auth requirements. Use direct image URLs, not pages that redirect.
Video generation is slower during peak hours
Video generation (/imagine-video, /extend-video) can take significantly longer during peak usage times (typically 9am-5pm PST weekdays). Tasks may take up to 10 minutes instead of the typical 1-5 minutes.
Workaround
Set appropriate timeouts in your polling logic. Use webhooks instead of polling for video tasks.
Percentage may jump from 0 to 100 on fast tasks
For quick tasks (like /seed or fast /upscale-1x), you may never see intermediate percentage values. The task goes directly from "0" to "100".
Workaround
Don't rely on percentage for progress UI on fast task types. Treat any non-"finished" status as "in progress".
Inpaint mask dimensions must match parent image
If the mask dimensions don't match the parent image, the inpaint may fail or produce unexpected results. There is no server-side validation for mask dimensions.
Workaround
Always generate the mask at the exact same pixel dimensions as the parent image.
Pan direction only works on upscaled images
The /pan endpoint requires the parent task to be an upscaled image (from /upscale-1x). Attempting to pan directly from a grid task will return a 400 error.
Workaround
Upscale the desired image from the grid first, then use /pan on the upscaled result.
Reporting Issues
If you encounter an issue not listed here, contact us at [email protected] with the task_id and a description of the problem.