Troubleshoot wallets and Safes
Wallet is on the wrong account or chain
Section titled “Wallet is on the wrong account or chain”Reject the prompt, switch in the wallet extension, and prepare the action again. The connected address and chain must match the handoff exactly.
Safe proposal is missing
Section titled “Safe proposal is missing”- Confirm the same chain, Safe address, nonce, and
safeTxHash. - Refresh Safe Transaction Service state.
- Check whether STS is delayed or rate-limited.
- Do not submit a second proposal with changed data unless you intend a different Safe transaction.
Signature is rejected
Section titled “Signature is rejected”Verify that the signer is a current Safe owner, signed the exact EIP-712 data, and has not already submitted. Owner or threshold changes can invalidate an older prepared attempt.
Transaction hash stays pending
Section titled “Transaction hash stays pending”The transaction may be unmined or below the network’s configured confirmation depth. Sync after more blocks. For Safe execution, txcast also requires the matching ExecutionSuccess event.
Nonce conflict or replacement
Section titled “Nonce conflict or replacement”Another Safe transaction may have consumed the nonce. Sync the run and compare the onchain event. Prepare a fresh attempt only after understanding the competing transaction.
EOA batch partially succeeded
Section titled “EOA batch partially succeeded”Inspect each transaction index. Never resend an already successful index. Determine whether the remaining request is still safe against the new state, then use the run’s current recovery options or cancel it.