A run stopped before the video was finished
The short answer
Nothing was charged. If the job offers Retry, it runs the stopped stage again with the same saved settings and keeps the stages that finished.
Retry the stopped stage
- Open the job. The stopped revision names the stage it stopped at.
- Choose Retry. The stages that finished are kept, and so are your approved words.
- If Retry is waiting, try again after 30 seconds. Retries are spaced out.
Each stage retries on its own before it stops, and you can retry it yourself a few more times. When the job says "This step has reached its retry limit", write to us with the job ID.
When there is no Retry
Some stops cannot be retried with the same saved inputs, and the job says so. Start a new video from the same footage. The clip stays in your library.
Questions
Was I charged for the stopped run?
No. Finished minutes are charged once, when the render finishes.
Will a retry sound different?
Not when the narration was saved: a retry reuses it. If no saved narration could be confirmed, the retry sends a new speech request with the same words and voice, and the take may sound different.
The messages this page covers
The job shows one of these under the stopped revision. Stops caused by full storage, a long narration or the allowance have their own pages.
- We couldn't analyze this video. This revision stopped before a video was created.
- Video analysis returned an unusable result. This revision stopped before a video was created.
- We couldn't write a script for this video. This revision stopped before a video was created.
- Script writing returned an unusable result. This revision stopped before a video was created.
- We couldn't write narration short enough to fit this video. This revision stopped before a video was created.
- The speech request could not be completed or confirmed. This revision stopped before rendering.
- These saved settings or words cannot be sent to the speech provider. Check the speech limits before starting another video.
- The generated audio could not be verified. No video was rendered.
- The narration could not be saved. No video was rendered. Temporary files will be cleaned up.
- We couldn't read the saved narration to time the captions. Your words, narration and timings are saved. No finished-video minutes were charged.
- The narration's word timings didn't match its audio, so captions can't be placed. No finished-video minutes were charged. Start a new video from the same footage to try again.
- The saved narration could not be verified for captions. No video was rendered.
- We couldn't prepare the captions. Your script, narration and timings are saved. Retry this step to continue.
- These captions could not be laid out safely. Your words, narration and timings are saved. No finished-video minutes were charged.
- The caption file could not be saved or verified. Retry with your saved narration and timings.
- The video could not be rendered from its saved footage and narration. No finished-video minutes were charged.
- The rendered video did not pass its media checks. No finished-video minutes were charged.
- The finished video could not be saved or verified. No finished-video minutes were charged.
- Production stopped before this revision could finish.
Did this not answer it? Write to a person; the email already names this page.
Write the emailRead next
- The stages of a run, in orderEvery video runs through seven stages, with your review after the script: video analysis, script, narration, caption timing, captions, rendering and description. Caption timing and captions only run when captions are on.
- How finished minutes are countedStarting a video holds its footage length, plus a small margin. When the render finishes you are charged the finished length and the rest comes back. A run that stops is not charged.
- Contact usWrite to info@jigframe.com. Include the job ID, the message you saw and what you tried; a person reads every email.