Why AI video renders fail — error codes, refunds and rewrites

Every generator fails sometimes. What separates an annoying afternoon from a productive one is knowing, within about four seconds of seeing red, which of four completely different things just happened — because three of them have fixes and one of them only needs you to press the button again. Here is the whole failure surface of the eroq video studio, what each state costs you, and the drill for a prompt that will not render no matter how many times you roll.

The four ways a render dies

They look similar in the interface and are not remotely the same problem.

content_blocked — the engine declined the prompt. This is a content decision, not a technical one, and pressing retry will reproduce it exactly. Rewrite or change engine.

generation_failed — the engine accepted the job and came back without a clip. This is the dice. The same prompt frequently renders on the next attempt.

generation_timeout — the job never came back at all. A render still processing past a ten-minute deadline is flipped to failed the moment you poll it, and refunded on the spot.

The refusals that happen before anything runs. A 403 plan_required means the engine you picked sits above your plan. A 503 model_unavailable means that engine is not open for business yet. A 402 insufficient_credits means the wallet is empty. All three are checked before the job is queued, so nothing is billed and there is nothing to refund.

What refunds itself

All of it. A failed render refunds automatically — content_blocked, generation_failed, a timeout that self-heals when you poll it. The pre-flight refusals never debit in the first place. Checking on a job costs nothing either, so polling a slow render is free and you can poll it as often as your nerves require.

Two practical consequences. First, a bad roll costs you time, not credits, which changes how aggressively you should retry — the answer is "more than you do". Second, your balance after a failed session should be exactly what it was before, minus the renders that produced footage. If it is not, the failure was actually a success you did not like, and those are billed.

Job ids expire twenty-four hours after creation, so a clip you never collected is gone from the queue the next day — though the render itself, if it succeeded, is in your Library with its full recipe.

content_blocked — rewrite, do not retry

Premium engines are moderated upstream by their providers, which is why Seedance, Kling, Hailuo and Veo are SFW-only here. Motion One · Wan is the uncensored video engine and is open to every account, free tier included.

So a block means one of three things. Either you have written something the policy genuinely refuses — sexual content involving minors in any form, real identifiable people, anything illegal, harassment; those are refused everywhere and forever. Or you are writing mature material on an engine whose provider does not accept it, in which case the fix is Motion One, not a rephrase. Or — most commonly and most annoyingly — you wrote something innocent that tripped a filter on a word.

That third case is worth a drill. Filters read nouns, not intent. Rewrite around the trigger rather than arguing with it:

• Name the shot, not the taboo. "A close-up of a bruise" describes a picture; the sentence you originally wrote described an event.
• Remove real names. Any real, identifiable person is refused; a public figure's name in a prompt is the fastest way to a block even when the scene is harmless.
• Replace abstractions with light and motion. Filters have very little to say about "sodium streetlight through venetian blinds".
• Keep bodies in wardrobe terms. "A woman in a wet trench coat" renders. Anatomical shopping lists tend not to.

A prompt rewritten this way, complete and ready to paste:

A woman in a wet trench coat stands under a flickering motel sign at two in the morning, breathing out into the cold, then turns toward the parking lot; slow push-in from a medium to a close-up, sodium light from overhead, neon reflections in the puddles at her feet, a tense and quiet mood.

Same scene, same mood, nothing for a keyword filter to grab.

generation_failed — change one thing at a time

This one is mechanical. Retry once, immediately — a meaningful share of these clear on the second attempt and it costs nothing to find out. If it fails twice on the same prompt, stop rolling and start subtracting. Change exactly one thing per attempt, in this order:

1. Cut the prompt to under eighty words. Long prompts fail more. Keep subject, motion, camera, light, mood, and delete the rest.
2. Reduce to one subject. Two people doing two things is the single most reliable way to get nothing back.
3. Drop the reference image. Image-to-video puts a hard constraint on the engine; a source photo that fights the prompt produces neither.
4. Change the aspect ratio to 16:9. Exotic ratios are the least-travelled path on most engines.
5. Change or clear the seed. Seedance engines honor a seed for reproducibility, which means a bad seed reproduces perfectly too.
6. Shorten the clip. A 3 s or 5 s version of a failing 10 s shot often renders, and tells you the prompt was fine.

If all six fail, the prompt is not the problem. The engine is.

When to switch engine

Engines have personalities, and half of "this will not render" is a shot asked of the wrong one:

• Faces and fluid human motion — Kling 2.5 Turbo, 1080p, and the one engine here with a native negative prompt for video, which is the right tool for "no extra fingers, no warping".
• Physics and dramatic light — Hailuo 02. Falling, splashing, catching light.
• Long single takes — Seedance 2.5 runs 4 to 30 s and takes a seed and first/last-frame interpolation, so a shot that needs to end somewhere specific has a mechanism.
• Mature material — Motion One, always. The premium engines will keep refusing, and no rewrite changes that.
• Cheap diagnosis — Seedance 1.0 Lite at 40 credits for 3 s. If the Lite version of your shot works, the prompt is sound and you are fighting the engine.

Plan gates are checked before the debit, so trying an engine you do not have access to is free information — you get a 403 naming the plan, not a charge. The full roster, with prices and plan access, lives on the pricing page.

Reading the failure in the API

If you are driving renders over the API, the same states arrive as structured fields: a failed job returns an error object carrying the code, with usage.credits_spent of zero, and a video.generation.failed webhook fires with the code attached. Poll GET /v1/videos/generations/{id} or take the webhook — both are documented in the video docs. Retry logic worth writing is short: retry generation_failed and generation_timeout twice, never retry content_blocked, and treat plan_required and insufficient_credits as configuration problems that need a human.

FAQ

Do I get my credits back when a render fails?

Yes, automatically. Blocked prompts are never charged, failed generations refund themselves, and a job stuck past the ten-minute deadline is failed and refunded the first time you poll it.

Why does the same prompt work on one engine and not another?

Premium engines are moderated by their upstream providers and are SFW-only. Motion One is the uncensored engine. Beyond content, each engine has its own length, ratio and resolution limits.

My prompt fails every time. Is it me or the engine?

Render a 3 s version on Seedance 1.0 Lite for 40 credits. If that works, the prompt is fine and the original engine is the problem. If it also fails, cut the prompt to one subject and one action.

Open the video studio and retry that shot — if it fails again, it costs nothing but the wait.