Separate a technical failure from a creative problem
A job that fails to complete needs a different response from a completed video with an awkward gesture. Start by checking the recorded status. If it is still processing, do not assume that refreshing the page or resubmitting the form will repair it. A new submission may be a separate paid request. If the status is failed, record the job identifier and the visible error without including credentials.
For a completed result, describe the problem in one sentence. “The right hand changes shape when it crosses the microphone” is actionable. “The model is bad” is not. Note the moment where the issue starts and whether the rest of the take is usable. A brief defect near the ending might be solved with a trim, while a changing face throughout the shot may require a new generation.
When the face or hands change
Reduce the amount of movement around the problem area. A performer turning sharply while gesturing across the face asks the model to manage several overlapping changes. Try a steadier head position, a simpler gesture, and a microphone placed slightly away from the mouth. If using a reference-supported workflow, check that the source face is clear and not heavily filtered or obscured.
Do not add dozens of negative instructions as the first response. Rewrite the desired action positively and concretely: the performer keeps both hands low, nods gently, and stays in a medium shot. Review whether the new take actually improves the identified issue. If the same defect remains, consider a wider framing or a cutaway instead of spending more on an unchanged difficult close-up.
When the camera or background becomes chaotic
Choose one camera behavior. A request for a static shot, an orbit, a rapid zoom, and a handheld feel contains conflicting directions. Start with a fixed camera or one slow movement. Simplify the environment by removing crowds, reflective signage, moving vehicles, and unnecessary props. A clear stage can still look polished through lighting and color rather than through a large number of animated objects.
If the scene changes unexpectedly, reduce the prompt to a single location and a single continuous action. Save multi-location storytelling for separate shots assembled in an editor. This also gives you more control over pacing. Once a simple version works, add one element back and test it. The purpose of the revision is to learn where the scene becomes unstable.
When the sound or wording is wrong
Listen to the output independently of the image. Determine whether the problem is unclear speech, altered lyrics, unwanted background sound, or mismatch with a separate track. Generated audio may vary from the prompt. If exact words matter, use a workflow that provides controlled audio and appropriate synchronization rather than assuming more descriptive text will enforce every syllable.
If you only need the visuals, mute the generated audio in your edit and use authorized sound. Then judge the mouth movement honestly: an overlay does not create precise lip sync. Use wider performance shots or nonverbal scenes when exact articulation is unavailable. If captions are added, transcribe the actual final recording rather than the rejected or intended wording.
Run a useful revision
Keep the original prompt, duplicate it, and change only the instruction tied to the defect. Record the result beside the earlier take. Stop when you have material that meets the project’s purpose; endless attempts at an undefined perfect result make it difficult to control time and credits. If the workflow remains unsuitable, change the shot plan. A simple alternate angle can solve an editorial problem that repeated generation cannot reliably solve at the frame level.
Prepare a concise support report
If the job state or credits appear inconsistent, collect the job identifier, submission time, chosen settings, and the exact visible message. Explain what you expected and what happened instead. A report such as “job completed but its download link returns an error” is easier to investigate than “nothing works.” Keep account passwords, API credentials, and unrelated personal files out of the report. Do not repeatedly submit the same request while waiting for the original job’s state to become clear.