Troubleshoot a pending request
Work out why a request hasn't completed, and what to do next, using PolicyVault's own status information.
PolicyVault's transaction pipeline is deliberately explicit about state: intent → build → sign → finalize → submit → reconcile, with a durable record at every stage, so a stuck or pending request is always diagnosable rather than mysterious. This page is a general troubleshooting path; for specific symptoms see the pages linked at the bottom.
Step 1: check the request's own state
Every request has an explicit state (see Request states) — for example, awaiting a wallet signature, awaiting approvals, submitted and awaiting chain confirmation, or a specific failure state. The state itself tells you what's actually happening; avoid guessing before reading it.
Step 2: if it's awaiting your signature
Nothing happens until the required wallet signs. Check that:
- the correct wallet/account is connected (see Wrong wallet connected),
- the wallet is on the correct network (see Wrong network),
- the signing dialog isn't showing DO NOT SIGN — if it is, something about the built transaction did not match what was requested, and that is itself the finding; do not sign, and treat it as a bug report.
Step 3: if it's awaiting approvals
Confirm the required approvers can actually see the request — see Approval not visible — and that enough of them have signed to meet the vault's threshold (see Approval states).
Step 4: if it was submitted but isn't confirmed yet
PolicyVault never treats "submitted" as success — it waits for genuine chain confirmation and the exact expected successor state before marking a request complete. This is expected to take some time on a live network; see Transaction pending for how long is normal and when to be concerned.
Step 5: if it failed outright
Check the refusal reason and error code against Reference → Error codes — every refusal PolicyVault produces carries a specific machine-readable code and a human-readable message, never a generic failure.
What never happens
A request is never silently lost. Because durable records are written before broadcasting and success requires proven chain outcome (not just a submitted transaction), a crash or network hiccup partway through leaves a recoverable, inspectable record rather than an ambiguous one. If a request genuinely seems to have vanished from the dashboard, that itself is worth reporting — see Responsible disclosure if you suspect a bug with security implications, otherwise use the project's ordinary issue tracker.
See also: Vault states, Request states, Approval states.