Generation Troubleshooting
Diagnosing and resolving a video generation that failed.
When a generation fails, the error is shown on that generation's entry in the Generations Rail. Start there — the message names the cause, and the fix usually follows directly from it.
Failed generations do not consume credits. Retrying is always safe, and a retry is often the whole fix when the cause was a transient provider problem.
Common causes
Insufficient credits
The generation is blocked before it starts if your balance will not cover it. Check the credit meter in the header, then either buy a top-up pack or reduce the cost by lowering the resolution, shortening the clip, or choosing a cheaper model.
The model is unavailable
Providers have outages and rate limits. You are told when your chosen model cannot run rather than being re-routed to another one. Wait and retry, or switch to a different model deliberately via the Custom layout.
Content policy
Providers screen prompts and reference images, and a rejection surfaces as a policy error. Rewording the script, or swapping a reference image that features a recognisable face, usually clears it. Different providers draw the line in different places, so a prompt one model rejects may run on another.
Timeouts
Long durations at high resolutions take the longest and are the most likely to time out. Retry, and if it recurs, generate a shorter clip or drop the resolution.
If it keeps failing
Simplify the configuration
Remove reference images, shorten the clip, and lower the resolution to get one successful generation. That tells you the pipeline works.
Add settings back one at a time
Regenerate after each addition. The step that reintroduces the failure is the cause.
Try a different model
Switch to the Custom layout and pick another model. If the same configuration succeeds there, the problem was provider-side.