Transaction pending

A transaction was submitted but isn't showing as complete yet — what's normal, and when to be concerned.

#Why "submitted" is not "done"

PolicyVault never treats a transaction being accepted for broadcast as a completed operation. It waits for the network to actually confirm the transaction, and for the exact expected successor vault state to be independently observed on-chain, before marking anything complete or updating a vault's recorded balance/budget. This means there is always a real, expected window between "submitted" and "confirmed" — seeing a request in a pending state right after signing is normal, not a problem.

#What normal looks like

The request's state (see Request states) should progress from SUBMITTING to SUBMITTED and then, once the network confirms it, to CHAIN_VERIFIED. The dashboard's operational status shows this as TRANSACTION_PENDING while waiting.

#When to be concerned

If a request stays in SUBMITTED far longer than normal Kaspa confirmation times, or moves to a state like RECONCILIATION_REQUIRED, SUBMISSION_REJECTED, or TERMINATED_UNKNOWN, see Troubleshoot a pending request for the general diagnostic path, and check the request's exact state and any associated error code against Request states and Error codes.

#What PolicyVault guarantees while a request is pending

The pipeline is built to be crash-safe: a durable record is written before broadcasting, so a crash or network interruption right before or right after submission is recoverable, not ambiguous. You should never need to guess whether a pending spend actually happened — reconciliation resolves it against actual, proven chain state, never a guess or a timeout-based assumption.

#Do not resubmit manually

If a request appears stuck, do not attempt to work around it by rebuilding and resubmitting the same intent outside the normal flow — this risks a double-spend attempt against the same funds. Let reconciliation resolve the original request first; the dashboard's recovery path is built specifically to avoid this risk.

See also: Vault states, Request states.