Failed AI generations: credit estimates and returns

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.

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 success, a task with valid actual usage at or below the reservation can settle to an integer credit amount. Any unused difference returns to the balance. A successful task may therefore finish below the initial reservation. That difference is not evidence of failure, and the estimate should not be read as an unchangeable final invoice for every workflow.

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.

When the service confirms failure and records the final failed state, it returns the credits reserved for that task to the balance. The creation detail shows how many credits were returned. The return is tied to that job, so duplicate callbacks or reopening the page do not add the same amount again.

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.

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.

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.

A return after generation failure changes the in-site credit balance and is linked to a task. A duplicate payment, a paid order that did not add credits, or an unusual order state is linked to the payment order instead. For that case, provide the order number, payment time, and visible order state rather than only a generation task identifier.

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.