Why AI work uses credit holds
Reserve before provider work, settle with the artifact, and release on failure.
TL;DR
- A credit hold reserves allowance before generation begins so concurrent work cannot all spend the same available balance.
- Successful work settles the reservation with the durable result; failed work releases it through the recovery flow.
- A pending hold is different from a settled charge, so inspect the operation status before starting another attempt.
- Use the Usage page and the related operation when investigating an unexpected balance change.
Why a balance needs a reservation step
Imagine two generation requests starting at nearly the same time. If each only reads the available balance and deducts credits at the end, both can believe they have access to the same remaining allowance. A reservation records the intended use before the expensive work begins.
PostCopilot uses credit holds for that purpose. The hold belongs to the operation that requested the work. It is part of the accounting lifecycle, not evidence that a finished artifact is already available.
For a user, the important distinction is between available allowance, reserved allowance and settled usage. Those states answer different questions: what can be started now, what work is already in progress and what work has completed.
Follow the operation through completion
A successful generation needs more than a provider response. Its usable artifact must be stored durably so the user can retrieve it. Settlement is associated with that completed result. If the work fails, the reservation is released through the corresponding failure path.
Abandoned work can leave a hold pending until maintenance expires it. A browser tab closing does not, by itself, prove that the server-side operation was canceled or that a provider did no work. Check the operation and its result before assuming the balance is wrong.
| State to investigate | What it means to check |
|---|---|
| Work is still running | Whether the expected artifact is pending |
| Artifact completed | Whether the related usage settled correctly |
| Work failed | Whether the reservation was released |
| Old pending operation | Whether recovery or expiration has completed |
This table describes the lifecycle to inspect. It is not a promise that every underlying transition happens instantly.
Avoid retries that hide the original problem
If the interface appears slow, first check whether the initial operation completed. Starting several new requests can create several distinct pieces of work, each with its own accounting. It can also make a support investigation harder because there is no longer a single attempt to examine.
Review the artifact library and operation status, then retry when the original result is clear. If the operation remains unresolved, keep its reference and the approximate time rather than repeatedly initiating new generations.
The same care applies to an output you dislike. A successfully completed result and a failed operation are different events. Do not infer the accounting outcome solely from whether you plan to use the generated asset.
Use the usage history as an explanation
PostCopilot maintains an append-only usage ledger and exposes usage information through the Usage page. Review that history alongside the operation or artifact involved. A total balance alone cannot explain which request reserved, settled or released credits.
When contacting support, include the relevant operation reference, what you attempted and when it happened. Avoid sharing account passwords or provider secrets. A specific operation is much easier to investigate than an unexplained screenshot of the final balance.
Plan creative work around clear outcomes
Before starting a generation, define the asset you need and review the input. A clear brief does not guarantee the perfect output, but it gives you a useful basis for judging the result and deciding what to change next.
Use PostCopilot to keep the related draft, artifact and campaign organized. Credit holds support reliable accounting behind that workflow; clear operation states and retrievable results are what make the process understandable to the person doing the work.
Frequently asked questions
Is a credit hold the same as a completed charge?No. It reserves allowance for an operation. Settlement and release are later outcomes associated with that work.
Does closing the browser cancel a hold?Do not assume so. Server-side work may continue. Check the operation's status and available artifact before starting another request.
What should I include in a support request?The operation reference, approximate time, intended action and the discrepancy you observed. Those details help connect usage records to the actual work.
Related reading: A safer social publishing workflow.
Related reading: Projects: a home for related creative work.