Credits, Cost Estimates and Failed Tasks

An estimate is not the final charge

The action button shows an estimate for the current inputs. Some tasks reserve credits first and settle using the accepted billing policy and actual result. A temporary balance change is not always the final cost, especially while processing continues.

Reconcile by task

Keep the operation time, feature and task identifier. Match consumption, refund and settlement records to that task. A workflow may contain separate recognition, conversation and generation steps. Failure of one step does not automatically refund other completed steps.

Troubleshoot in order

1. Determine whether the task failed or is still processing.
2. Read the error and check the prompt, file type, dimensions and model limits.
3. Look for the corresponding refund or settlement in credit history.
4. Correct the inputs before retrying.
5. If the result and records disagree, report the time, feature, task identifier and exact error.

Common causes

Fix invalid parameters using the on-screen validation. Revise inputs after content-policy failures. For network issues, check the task state before starting another generation. A missing browser result does not prove the upstream task never completed.

Recharges and extension storage

Payment orders, credit consumption and extension storage are separate records. Use the payment order identifier for recharge issues and the storage panel for import issues. Current pricing and your actual account records are the source for amounts and allowances.

Related guides

• Canvas basics