Skip to main content

​
Output retention

Result files are served from temporary CDN URLs that stay valid for 7 days after a task completes. Treat every returned URL as a temporary delivery URL, not as your application’s permanent asset. After a task reaches completed:
  1. Download the required file from output.image_url or output.image_urls.
  2. Store it in storage controlled by your application.
  3. Save your durable URL alongside the Legnext job_id.
  4. Serve the durable copy to users instead of depending on the original URL.
Do not schedule the download for the end of the 7-day window. Networks, providers, and storage migrations can make a delivery URL unavailable earlier. A production integration should persist the output as part of completed-task processing.

​
Task and follow-up window

Task lookup and operations that depend on an existing Midjourney result are available for three days after the source task is created. Complete variations, upscales, and other follow-up operations inside that window. Use available_actions to choose a likely valid action, but still handle a 400 rejection. For some edit-derived images the field can advertise an action that the provider cannot perform.
Output retention, task lookup, and follow-up operation validity are separate. Storing an image yourself does not extend the period in which Legnext can query or perform an action on the original task.
See Task lifecycle for polling, webhook, and retry guidance.