Skip to main content

Billing, settlement, and retirement

Insufficient Service Credits​

Confirm the active organization and read available versus reserved credit. Review the deployment quote and policy cap. Customer Stripe checkout and new Service Credit issuance are release-gated. If an existing organization lacks available credit, stop before retrying and contact support; do not call an internal funding endpoint. The customer does not fund a crypto wallet.

A balance change does not necessarily retry a blocked deployment. Return to the Action Plan.

The run ended and a charge is still open​

Coverage can report ended-unsettled when occupancy is vacant and a reserve, review-pending hold, or older liability remains. That is remaining money, not missing capacity. Do not relaunch to close it. See Intended capacity versus remaining charges.

Reserve remains open​

Match the reserve to Application UID, deployment, job, and current execution evidence. It can remain while a job is in progress, terminal chain evidence is pending, or financial reconciliation is under review. Do not treat it as a final charge or release it by starting duplicate work.

An ordinary managed Not billed — no report filed row is already closed: zero was charged and the full linked reserve was released. It needs no customer action and must not show an amount in review. If a no-report reserve is still open, the strict deadline or required scanner evidence has not qualified for that closeout; preserve the evidence and wait or escalate the typed blocker.

Final amount is under review​

Preserve quote, reserve, policy cap, job schedule, chain evidence, and transaction IDs. Liskov must fail closed when the sources are ambiguous. Customer-facing support should investigate; no public command can assert a made-up final amount.

Retirement waits for schedule end​

Starting retirement stops new Liskov work but existing Acurast jobs continue to their chain-owned end. Compare latestKnownScheduleEndAtMs with current time and the execution blockers. A locally ended process is not by itself proof that the registered schedule ended.

Retirement waits for financial tail​

All reserves, final charges, releases, and reviews must close. Match each financial blocker to a transaction/evidence authority. Retirement completes only when execution, financial, and ambiguity blocker counts are exactly zero.

Cancel or escalate​

Cancel before irreversible finalization when the supported action remains available:

proof liskov application retire cancel APPLICATION_ID \
  --reason "requested in error" \
  --yes

The Application stays paused.

If the cancellation returns retirement_already_completed, it succeeded at something else. The retirement finalized before the cancellation was applied, so there was nothing left to cancel; the response carries the immutable receipt and the CLI exits 0. Retain the receipt and stop — this is not an error to escalate.

Escalate only an obligation the Console or CLI marks as waiting on operator review. An obligation waiting on Liskov or on the Acurast chain is progressing correctly, and its age alone is not evidence of a fault. When you do escalate, send support the retirement ID, phase, blocker category and code, resource IDs, assessment digest, how long the assessment has been unchanged, and timestamps. Do not ask for a force-complete.

After completion, verify and retain the immutable receipt, and note its receiptKind: a safe_retirement receipt proves a zero gate, while a legacy_immediate_tombstone records a historical deletion that does not.