A video that is still running, a task that failed and a completed shot you dislike need different next steps. Start with the task status and its explanation. Rewriting a prompt cannot fix every cause of failure.
In JMovie, inspect the video task and any available details beside the status. Keep the original request and references while you work out what to change. The examples below are troubleshooting guidance, not a diagnosis of a particular task.
If the task is still running
An asynchronous video request can spend time waiting as well as generating. MiniMax’s video workflow guide describes submitting a task and checking its status before retrieving the result.
A longer wait alone does not prove the prompt is wrong. Check the latest status before submitting the same request again. A second submission may create another task rather than speed up the first one.
If the status no longer changes and you need help, keep the task identifier and the approximate submission time. Share the details through the relevant support channel so the actual request can be traced.
If the service reports a temporary problem
A reported capacity, network or temporary service error is a reason to consider retrying the same request after the original task has failed. Keep its prompt unchanged for that retry so you can tell whether the service recovered.
Avoid repeatedly clicking a submit control while the first action is still pending. Read the new task state and any displayed quote before another submission. Do not assume a failed attempt and its retry have identical billing treatment.
If the same error repeats, save the error details and stop making identical attempts until there is more information.
If an input or setting is unsupported
Check the selected model’s current input mode, file requirements, duration, aspect ratio and resolution. A valid image file can still be incompatible with the chosen combination of settings.
Make sure an uploaded file is available and that you can open it. Confirm whether it is being used as a reference, a first frame or a last frame. Those roles are not interchangeable.
Correct the specific issue named in the message, then review the request again. The reference-input guide explains how to match the input role to your intended shot.
If the message identifies a content restriction
Read what the message actually identifies. Check the material you supplied, including images, requested voices, music and lyrics. Replace material you cannot use with an original or permitted alternative.
For an audio-specific problem, a supported silent-video workflow may be suitable if the remaining visual request is permitted. Plan any later soundtrack with the same care about permissions.
Do not keep paraphrasing a restricted request to seek a different screening outcome. If the explanation appears inconsistent with the submitted material, retain the task details for support review.
If the video completed but the shot is wrong
This is a quality revision. Name the visible problem: the face changes, the camera crosses the room, the bottle floats or the speaker delivers an extra line.
Change one relevant part of the plan. For example, take this vague performance instruction:
The character is nervous and everything feels tense.
Give it an observable sequence:
The character rests one hand on the closed envelope. She hears a knock, stops moving and looks toward the door. Keep the camera fixed on her face and hand.
These are untested examples of making an instruction easier to review. They do not guarantee a successful result. If the problem persists, simplify the action, improve the reference or separate the shot into smaller pieces.
Record the result of each change. That gives the next attempt a reason, and gives support something more useful than a series of unexplained retries.