A generation failed or is stuck
You’re never charged for failures. Reserved credits refund automatically, so retrying is free.1
Give it time
Video is the slowest node type. Let it run before assuming it’s stuck.
2
Retry the node
Run it again. Most failures are temporary.
3
Simplify your prompt
A shorter, clearer prompt often succeeds where a long one stalls. More tips in generation help.
4
Check your balance
Generations need available credits to start. Check the wallet in Settings → Billing.
A Tools run failed
Tools (Upscale, Lipsync Studio, Voiceover, and the rest), run the same billed generation as a canvas node, without a canvas around it. The same fixes apply:1
Check the input
Every tool expects something specific: a clear face for Face Swap, a script for Voiceover. A mismatched or low-quality input is the most common cause of a poor or failed result.
2
Retry it
Most failures are temporary, and a failed run refunds its reserved credits automatically, retrying costs nothing extra.
3
Check your balance
A run can’t start without enough available credits. Check the wallet in Settings → Billing.
A render is stuck
Renders take real time: longer compositions and higher resolutions take the longest, so give one a fair chance before assuming it’s stuck.1
Keep the project open
Closing the project while a render runs can interrupt it. Leave the tab open until it finishes.
2
Check your connection
A dropped connection mid-render is a more common cause of a stall than the render itself. Confirm you’re still online and retry.
3
Retry the export
Reopen the export panel and start it again: most stalls clear on a second attempt. See the export guide for the settings that affect render time.
4
Still stuck after a retry?
Contact support with the project name and roughly when you started the render.