When AI video generation stops before you have a usable draft, start by identifying the stage where it stopped. A missing entry point, a blocked action, a processing message, an incomplete draft, and an export error each call for a different next step. Capture the exact notice and work through the matching branch below before you change the project.
Record the failure before changing anything
Make a short note with the page URL, date, last control you selected, exact error or progress label, and input type. Include whether the issue appeared before processing, while a request was processing, or while exporting a finished draft. That small record makes it easier to choose the right branch and gives CapCut Support the details needed to investigate.
Find the point where the workflow stopped
Start with the stage, not with a new prompt. CapCut separates access, processing, and export troubleshooting, so the visible state is the clearest guide to the next action.
The entry point or control is missing
Open the AI video generation workspace after you have recorded the original symptom. Compare the workflow you see with the documented path and keep a note of the version information shown by CapCut. CapCut's guidance for AI tools also helps you separate a missing entry point from a request that has already started processing.
A visible action is blocked
Read the notice before changing the input. A message about permissions, policy, or access tells you which support path to use. Save the notice and a sanitized screenshot, then use CapCut's AI access troubleshooting guidance to prepare a clear support request. Do not change unrelated project settings while you are still identifying the message.
Processing starts and then stops
For an AI video generation action that stalls or ends with an error, preserve the status label and a short summary of the input first. CapCut's processing troubleshooting guidance distinguishes processing from ordinary editing and export. Check whether the message points to the request itself, then keep the original evidence together before you make a new attempt.
Use the symptom-to-action branch table
After recording the failure, choose the first row that matches what you can actually see:
Do not mix branches. A missing entry point needs an access check, while a complete draft with a file error needs an export check. If the symptom changes after one action, keep both the original and new messages so the next report describes the sequence rather than only the final state.
Separate an incomplete draft from an export problem
Open the draft and check the timeline, selected media, captions, and audio before you classify the issue as export-related. Missing scenes or media belong to the project-state branch. A complete draft that will not produce a file belongs to the export branch.
Use CapCut's export troubleshooting guidance when the draft is ready and the error appears during file delivery. If captions are part of the project, the caption export guide gives the details to include in your evidence note.
Send a useful support report
Keep the report focused on the observed issue:
Page URL: Date and time: Last control selected: Exact message or progress label: Input type: text / image / existing project Stage: missing / blocked / processing / export What changed immediately before the message: Screenshot: personal and project details removed
Use the exact words shown in the message. Remove personal media, project names, and other private details before sharing a screenshot.
Choose the right next guide
When the symptom is specific, move to the guide that matches it rather than repeating the general checks. Use the 99% guide for a near-complete progress bar, the policy guide for a guidelines notice, the voiceover guide for narration failures, and the generation-error guide for a direct failure message. Once the issue is resolved, return to the CapCut troubleshooting guide collection to continue with the next AI video generation task.