Why a generation fails, and what happens to the credits

Generations fail for three reasons, and only one of them is your problem.
Our side: automatic refund, 60 seconds
The first reason is us or the model being down: a queue times out, a file does not come back. Nothing was produced and nothing should be charged, so the credits are returned automatically within 60 seconds and the refund shows up as its own row in your credit history. You do not open a ticket for this.
The safety filter: a refusal you can read
The second is the prompt hitting a safety filter. The generation is refused rather than failed, and the refusal comes back as an error you can read instead of a silent empty box. Rewording the shot is usually all it takes.
The one that costs money: it worked and you hated it
The third is not a failure at all: the generation worked and you did not like it. A retake is a new generation billed at its own price, because the model ran again in full. Nobody in this market absorbs that, and a company that says it does is either lying or pricing it in somewhere else.
The way to make this cheap is the way working directors do it: block the scene on a 4.73-credit model, and only re-run the shot that is actually wrong, not the scene around it.
Two smaller things that surprise people
Your plan sets how many generations run at the same time: 2 on Entry, 6 on Plus, 8 on Pro and Studio. An extra one past the limit waits its turn rather than failing.
Credits held by a generation in flight are subtracted from your balance while it runs, which is why the number can look lower than you remember. The billing page shows the held figure separately for exactly that reason.

Free to start
40 credits when you sign up
40 free credits, yours for 14 days. Go make something great.
- SOTA models
- Infinite canvas
- Director stage
- MCP access
Got questions left?
How do I know a refund actually happened?
It appears as its own labelled row in your credit history, within 60 seconds of the failure. The balance and the row always match.
A generation is stuck at waiting. Is it broken?
Usually it is the concurrency limit: your plan runs a set number at once and the rest queue. It starts on its own when a slot frees up.
If the video comes back with a glitch, is that my cost?
A run that returns a broken file counts as failed on our side and refunds itself. A run that returns exactly what you asked for, just not what you hoped, is a retake.


