ElanoryaJewelry AI
Why the app won't start your generation
A generation that never begins is a precondition failure, not a model failure. Instead of one generic error, the app names which check stopped the run: an unverified email address, terms that have been updated since you last accepted them, or a credit balance that is not enough to start. Because each state is worded separately, finding the blocker is a lookup rather than a diagnosis.
The three gates a generation passes before it starts
These checks run before any image work begins. Each has its own wording, so the message on screen is already the answer to why the generation is blocked.
- Your email address has to be verified.
- Until the address on the account is confirmed, the app will not start a run. The message names the verification step rather than describing a general problem, so the next action is to finish verification and try the same piece again.
- The current terms have to be accepted.
- When the terms have changed since your last acceptance, the app asks for the new acceptance before it will start a generation. This gate is independent of verification: clearing one leaves the other exactly as it was.
- The account has to have enough credit to begin.
- An insufficient balance is the third named gate, and that is the whole of its role on this page. What a run costs and when the charge happens belong to the page that owns the charging mechanism, and are deliberately not explained here.
How to find out why the generation is blocked
The order matters, because the first step decides whether this is the right page at all.
Check whether a run exists at all
If the app is showing a job in progress, the generation did start and nothing here applies. A run that has begun is a waiting question, and the page on waiting for a generation is where that belongs.
Read which precondition the app named
The blocking message exists to identify the gate. Its job is to tell you whether the account state, the terms or the balance stopped the run, so you do not have to work through all three.
Clear that one gate
Finish the verification, accept the current terms, or add credit — whichever was named. The gates are independent, so start with the one you were actually shown.
Start the same piece again
Return to the same photograph and run it again. A blocked attempt never reached the model, so this is a fresh start rather than resuming something half-finished.
If a different gate is named next, treat it as a second precondition
Different wording means a different check, not the first one failing again. Clear it the same way and start the run once more.
What does not stop a generation from starting
The category is not a gate. Rings, bracelets, necklaces and earrings all pass through the same account-level checks before a run begins, so switching category will not turn a blocked generation into a running one.
A setting you cannot find is not a gate either. There is no size, background or aspect-ratio control in the app and output size is fixed, which means an unmade choice can never be the reason the run did not start.
Editing a photograph you already have does not bypass the checks. The image edit tool starts with its preservation switches on and adds a named line to the request for each switch that stays on — that behaviour is described on the image edit page, and it applies after a run has been allowed to start, not before it.
A result you did not like is a different situation entirely. The report flow opens from a finished image and carries named reasons, the first being that the product changed. A generation that never started has no result to report, so clearing the named gate is the only move available.
What comes back in each case
The three outcomes are easy to confuse on screen, because two of them show no image.
| Situation | What comes back | Where to go next |
|---|---|---|
| Blocked before the run | A named precondition and no image — no partial file and nothing in progress | Clear the gate the app named, then start the same piece again |
| Started and still working | A job in progress; the image arrives when the run finishes | The page on waiting for a generation covers what the progress states mean |
| Finished with a result | One image at the fixed output size, with no size, background or aspect-ratio options to choose from | If the piece came back changed, the report sheet on the result carries named reasons |
Where a blocked generation creates extra work
The cost of a blocked run is usually not the run itself but the photography around it.
The interruption lands in the middle of a shoot.
Clear account-level preconditions before the pieces are laid out, so a single collection is captured under one lighting setup.
The piece is re-staged because the absence of an image is read as a bad result.
Confirm that no result exists before touching the piece. A blocked run says nothing about the photograph you uploaded.
Two people on the same account work against each other.
Let one person clear the named gate, then retry once rather than in parallel.
What this page does not cover
- It does not explain what a generation costs or when the charge happens. Credit appears here only as one of the three named gates.
- It does not quote the app's messages word for word. Wording can change; what matters is which precondition the message names.
- It does not list or count server error codes, and it does not describe what the image model does internally.
- It does not cover runs that have already started. Progress states belong to the page on waiting for a generation.
- It does not promise anything about a result once a run does begin. The preservation rules are instructions sent with the request, not guarantees about the output.
- It does not cover transparent output, which is the background remover's subject rather than this page's.
Questions
Why won't the app start my generation?
Because one of three named preconditions has not been met: the email address on the account is not verified, the current terms have not been accepted, or the balance is not enough to begin. The app names which one applies, so a blocked generation is something you read rather than something you diagnose.
I verified my email, so why is the generation still blocked?
Verification and terms acceptance are separate gates. Clearing the verify-email-to-generate step does not accept updated terms, and neither of them affects the balance. If the second message is worded differently from the first, it is naming a second precondition.
How do I tell a blocked generation from a slow one?
Look for a job in progress. A generation that cannot start leaves nothing running, while a generation that has started shows progress and finishes on its own. The page on waiting for a generation covers the second case in detail.
Can I report a generation that never started?
No. The report flow is attached to a finished image and offers named reasons for what went wrong with that result, beginning with the product having changed. A run that was blocked has no result, so the step is to clear the precondition the app named and start again.