API ReferenceTransactions, wallets, and signaturesEnumeration
WalletOperationStatus
Lifecycle state of a single WalletOperation. Use isTerminalOperationStatus to tell whether it can still change.
Enumeration Members
| Enumeration Member | Value | Description |
|---|---|---|
AwaitingConfirmation | "AwaitingConfirmation" | Submitted; waiting for the transaction to be mined. |
AwaitingSignature | "AwaitingSignature" | The wallet is currently prompting the user to sign or approve. |
Confirmed | "Confirmed" | Terminal. Transaction mined successfully. |
Failed | "Failed" | Terminal. The step did not complete: the user declined in the wallet, the transaction reverted, or the wallet returned an error. The WalletOperation’s validationErrorResponse field says which, for example { root: ['RejectedByUser'] }. Problems execute() finds while revalidating never set this status: it resolves invalid or failed and leaves every step as it was. |
Indeterminate | "Indeterminate" | Not terminal. The outcome is unknown, and the steps after it stay Queued. With a transactionHash, confirmation timed out: the transaction may still land, and calling execute() again checks that hash instead of resending. With no transactionHash, the connection failed during the send: calling execute() again leaves the step as it is. The SDK never resends it, so check the wallet’s activity before you build a new workflow. |
Queued | "Queued" | Not started. |
Rejected | "Rejected" | Terminal. This step never ran: an earlier step failed, or every caller canceled the run after its first wallet prompt. |
Signed | "Signed" | Terminal. Signature obtained; the bytes are on the WalletOperation’s signature field. |