Recover a pending or failed transaction

Read the status before trying again

An error message does not always mean nothing reached the network. A provider can lose its connection after receiving a signed transaction. Start with the operation or transaction identifier already shown in the app.

Do not repeatedly click Submit to make a pending action faster. First check whether the original operation was submitted, confirmed, rejected, or is still awaiting a reliable answer.

Choose the case that matches your screen

• You rejected a signature: review the request again when ready. No signature was authorized by that rejection.
• Wrong account or network: switch to the intended account and test network, then reopen the operation. Do not sign a request prepared for another account.
• Approval confirmed, action failed: the allowance may still exist. Check the approval and original action separately before continuing; another approval is not proof of completion.
• Transaction submitted, confirmation delayed: retain its identifier and check the original status. Wait for chain confirmation instead of creating a replacement.
• Quote or verification expired before submission: request a fresh review. Do not reuse an expired signature or change its amount.
• Bridge source confirmed, destination pending: the transfer is unfinished. Track the same message at its destination; do not send the source assets again.

After a refresh or closed tab

Return to the same official domain, environment, account, and vault. Open My Solslot or the relevant action page and use the existing operation where available. Staging records and public Alpha records may be separate even when the wallet is the same.

If no recovery action appears, keep the transaction identifier and contact support. Do not assume that clearing browser storage cancels a network transaction.

An invalid-vault verification message

A proof is bound to a particular vault and network. A saved proof can become unusable when the account, vault, environment, or current on-chain state changes.

Browsing education and public properties should not require repeated verification. Reconnect the intended vault before an action. If the warning persists, report the page, environment, and non-sensitive error text.

What to share with support

• The official page and whether you were using staging or public Alpha.
• The action, approximate time, and non-sensitive error text.
• An operation or public transaction identifier through the approved support channel, only if needed.
• Never a seed phrase, private key, password, backup contents, login link, identity document, or authentication token.