Account, credits, and troubleshooting
Credits: estimates, reservations, charges, and expiry
A lower available balance during a task is not necessarily final spending. Moderation blocks and service failures differ.
Open featureView subscription and credit recordsOn this page
Check the final task state
| Stage | Meaning |
|---|---|
| Estimate | Current inputs/settings and full output count; not every model settles at the estimate. |
| Reservation | Temporarily reduces available balance, not consumption of all reserved credits. |
| Settlement | Consume under actual rules and release excess; actual usage can differ. |
Reserved does not mean spent
Not every failure is free or charged
Retry, regenerate, and paid-tool repeats are new requests and may charge again. Keep the error and distinguish content adjustment, balance, waiting, and resubmission.
| Situation | AI images | AI chat |
|---|---|---|
| Generation/moderation service failure | Release the corresponding reservation. | Release corresponding reserved credits under final failure rules. |
| Explicit input moderation block | Settle at estimated credits; do not resubmit unchanged. | Release reservation; different from image input-block rules. |
| Explicit output block | Settle for actual returned count. | Settle actual produced usage. |
| Browser preview/network failure | Not necessarily a generation failure; check saved status and connectivity. | Disconnection is not proof no reply was produced; check the turn. |
What can change the cost
- Models, size, quality, inputs, and output count can change image charges. Estimate the full request, not one output.
- Chat uses actual input/output and model rules; thinking and enabled web features can affect costs. Characters are not an accurate token-cost conversion.
- Prompt optimization uses its selected chat model's rules; rewriting is not guaranteed free.
- Grid, Transform, and Annotation need no generation credits but use storage. Outpaint is paid.
- Check payer for every shared task. Self-payment does not create a personal canvas.
Every batch has its own lifetime
Inspect remaining amounts and expiry in Subscription records and Credit expiry. Membership, registration trial, and purchases may overlap with different terms.
Period-credit expiry differs from membership expiry. Pack lifetime follows purchase rules. New subscriptions and dedicated sharing do not refresh old credit batches.
Task or dedicated-share reservations retain original expiry. Released expired credits do not gain a new lifetime or become available again.
If balance/budget looks sufficient but submission fails, inspect pending reservations, dedicated funds, expiry, access, and storage. Current account and settlement records determine the result.
Membership and registration trial credits can coexist with separate terms. This teaching account currently has Flagship test benefits. Example balances are neither yours nor fixed monthly allowances.
Actual interface · Tutorial example, not your accountMonthly renewal is not unlimited accumulation
For example, Free membership beginning October 10 reaches its next monthly boundary on November 10. Unused old-period credits do not add to the new period. This explains the calendar rule, not your exact account time.
Free, trial, and purchased batches can coexist, so total balance need not equal one monthly allowance. One period expiring does not zero every source.
A task reserved before expiry and failed afterward does not revive its expired credits upon release. Dedicated sharing also does not pause expiry.