Most generations work. When one does not, the status tells you what happened, and in almost every case you have not lost the credits.
The statuses
| Status | What it means |
|---|---|
| Pending | accepted, not started yet |
| Queued | waiting its turn |
| Processing | being made now |
| Completed | finished, in your library |
| Partial success | part of a batch worked, part did not |
| Failed | something went wrong; nothing was produced |
| Cancelled | stopped, by you or by the system |
| Rejected | not accepted — usually a content rule |
Were you charged?
No, unless something was produced.
Credits are held when you start a generation and only actually spent once the result is saved. If it fails, is cancelled, or is rejected, the hold is released and the credits return to your balance.
This is why your balance can briefly show less than you expect while work is running — that amount is held, not gone. It comes back if the work does not land.
For a batch, this applies item by item. You pay for the items that produced something and not for the ones that did not.
If a balance still looks wrong an hour later, contact support with roughly when it happened.
Failed
Something broke. Usually temporary.
- Try again. A retry succeeds more often than not, because the common causes are transient.
- Try a different model. If one model keeps failing on a prompt that works elsewhere, the model is the problem.
- Simplify. Very large sizes, unusual combinations of settings, and long prompts all raise the chance of failure.
- If it keeps failing, contact support and say roughly when you tried and what you were making.
Rejected
The request was refused rather than attempted. Nearly always the content rules: something in the prompt, or in an image you supplied, is not permitted.
Rewrite and try again. If you believe the rejection is wrong — an ordinary word that happens to appear on a list — contact support and quote what you were trying to make. That is how false positives get fixed.
Rejections do not cost credits.
Cancelled
Either you stopped it, or the system did — most often because it exceeded the time allowed. Long video generations at large sizes are the usual case.
Try a smaller size, a shorter clip, or a faster model.
Stuck in Queued or Processing
The queue is busy. Everyone’s work is interleaved so that no single account monopolises the capacity, which means a wait when demand is high.
You do not need to stay on the page. Leave, come back, and it will be in your library. Turn on notifications if you would rather be told — see notifications.
If something has genuinely been sitting for far longer than that kind of work usually takes, contact support. Work that gets orphaned is detected and its held credits returned, so a stuck job does not quietly cost you anything.
Completed but the result is wrong
Not a failure — the system did what was asked. This is a prompt problem, and the fix is in writing a prompt.
The quick checks:
- Is what you want actually in the prompt, or only in your head?
- Are you fighting a known weakness — text in the image, exact counts, hands?
- Starting from an image: is strength too high or too low? See starting from an image.
Nothing appeared at all
- Check the view you are looking at. If the gallery is filtered to Favorites or a folder, new work is not in it. Switch to Recent.
- Reload the page.
- Check your credit balance — if you ran out, the generation may not have started.
When to contact support
Worth reporting: credits that did not return after a failure, work stuck for hours, the same failure repeatedly on a prompt that used to work, or a rejection you think is a mistake.
Include roughly when it happened and what you were making. See contacting support.