When an operation is pending
Keep the original signed operation and resolve its state without reusing a key.
Why an operation can stay pending
A signature can be saved before a relay accepts it, or a network response can be lost after submission. In either case, the one-time key may already be exposed. A timeout is not proof that nothing happened.
Refresh, then review an exact retry
- 1
Keep the account and journal
Do not clear browser storage or replace the saved account to make the pending state disappear.
- 2
Refresh status
Qozmo reads the chain and reconciles known key state. Use the explorer address or known transaction link for additional detail.
- 3
Inspect the signed operation
The pending panel shows its operation hash and stored public signed fields.
- 4
Retry exact bytes if appropriate
With a relay connected, select Review exact retry and confirm your password. Qozmo resubmits the stored operation without creating a new signature.
Read execution status
| Activity label | Meaning |
|---|---|
| Execution succeeded | Verified operation evidence reports successful execution. |
| Execution reverted | The operation was included but its execution failed; the key was consumed. |
| Pending / check explorer | The signature is retained and its final outcome is unresolved. |
| Key consumed / verify execution | Key state advanced, but a matching successful execution receipt has not been verified. |
If it cannot be resolved
Preserve the original device, encrypted archives and journal. Exact retry retains the original fee fields; it does not raise fees or rotate a recovery authority. Qozmo does not expose a recovery-activation override or clear the one-time-key record.