Failed AI generations: credit estimates and returns
Understand credit estimates, final charges for successful jobs, returns after failed tasks, what to do while processing, and when payment is a separate issue.
To decide whether a generation used or returned credits correctly, do not rely on the balance shown immediately after clicking Generate. A task moves through submission, queueing, generation, success, or failure, and some successful jobs settle against verified actual usage.
The task record in My Creations is the best reference. Check its final state, visible credit amount, failure information, and any return notice before you wait, retry, or contact support. Submitting again creates a separate job; it does not push the first one forward.
1. Confirm the visible estimate before submission
The estimate can depend on the model, mode, output count, duration, resolution, or other current controls. Read the workbench value again before sending and make sure you have not selected a higher tier, extra output, or different workflow by mistake. A model page explains the pricing unit, but the estimate on the current form is the submission reference.
You can keep a note of the important settings or a screenshot without private content. Do not treat an old image as a permanent price list because availability, controls, and rates can change. If the balance is insufficient, the system rejects the new job before it begins; that is not a generation that later failed.
2. Understand reservation and final settlement
When a task is created, the service uses the provable cost of the selected configuration to reserve credits from the balance. This prevents an asynchronous job from completing without enough credit. For a fixed-price task, the reservation is normally the final amount. Usage-based jobs may reserve a safe amount derived from the current settings.
After a successful usage-based task, verified usage determines the final charge. Unused credits return to their original source, with the original expiry date. Credits that have already expired do not increase your spendable balance. A lower final charge does not mean the task failed. If usage is still being checked, keep the task record and wait for settlement.
3. Check the task’s final status first
Open My Creations and match the model, creation time, and prompt summary. A queued, waiting, or generating label means the job is still running or waiting for an update. Success means a text or media result is available. Failure should show a failed state and may include a user-readable reason.
Closing the browser, losing the connection, or seeing a frozen progress animation does not prove that the server task failed. An asynchronous job can continue after you leave the workbench. Returning to the task record is more reliable than repeatedly pressing Generate or judging the outcome from one browser screen.
4. How a failed-task credit return appears
Once failure is confirmed, the task’s credits are returned to the source they came from. Credits from a permanent pack can be used again. Membership credits retain their original monthly expiry date; a return cannot carry them into a new period or convert them into permanent credits.
For example, if a task uses 20 membership credits and fails after that monthly period has ended, the return is recorded but those 20 credits are no longer spendable. Check the source, expiry date, and transactions in your credit history.
If the task still says it is processing, it has not entered the failure-return step. If failure is visible but the return notice is not, refresh the detail and balance first. If they remain inconsistent, keep the record and contact support with the task identifier, time, model, and visible account information.
5. Do not duplicate a task that is still running
Generation time varies with media length, queue conditions, model, and complexity. When a job remains active longer than expected, wait and refresh My Creations. Another click does not accelerate the original task. It creates an independent job, reserves credits again, and may produce another result.
Submit again after the first task has a confirmed failure, the input needs correction, or support asks for a controlled reproduction. Keep the model and main settings the same while changing only the file or field that caused the issue. This makes results easier to compare and keeps each credit entry understandable.
6. Collect evidence before contacting support
Prepare the task identifier, creation time and timezone, model name, final status, displayed credit amount, failure message, and whether a return label appears. For a media problem, share diagnostic facts such as type, approximate size, or duration, but do not post private files, full confidential prompts, payment credentials, or account secrets in a public channel.
Mention whether you refreshed the creation detail, whether a duplicate job was submitted, and the exact difference between the visible balance and your expectation. One task with a clear timeline is easier to verify than a general report that credits disappeared. Keep the failed record until the review is complete.
7. Keep generation credits separate from payment orders
A failed-generation credit return is a task transaction, not a cash refund. For a duplicate charge, missing purchase credits, or an incorrect order status, provide the payment order number, payment time, and visible order status.
Permanent credit packs do not expire. Membership credits are issued monthly and expire at the end of their monthly period, including on annual plans; annual payment does not release a full year’s credits at once. CNY memberships run for a fixed term without automatic renewal. USD card subscriptions renew on the selected billing cycle; use subscription management to cancel future renewal. See pricing for offers, billing periods, and available payment options.
There is currently no self-service refund option for topped-up credits. Report duplicate charges and other payment issues through support with the order information; handling follows verification, subject to any rights provided by applicable law. Never send a full card number, verification code, password, or secret key.
In this article
Credits and failed tasks FAQ
Are credits automatically returned when a task fails?
After confirmed failure, credits return to their original source. Permanent credits become usable again; membership credits keep their original expiry date. Expired credits do not increase your spendable balance, even if a return is recorded. Queued or generating tasks have not failed.
Why can the final charge for a successful task differ from the estimate?
Some jobs reserve credits from the selected parameters and settle against verified actual usage after success. When final usage is lower, the difference is returned. Use the visible task record as the account reference.
Should I submit again if a task has been processing for a long time?
Not immediately. Refresh My Creations and wait for a final state. A repeated submission creates a separate task and reserves credits again. Retry after a confirmed failure or support guidance.
Check the task record before retrying
Open My Creations to review status, failure information, and any credit-return notice, then decide on the next step.