Handling Failed or Submitted Transactions

sometimes a transaction doesn’t go through on the first attempt primevault makes it easy to either retry the same transaction or create a new one without re entering all the details this guide explains how to understand transaction status in primevault what to do if a transaction is failed what to do if a transaction is stuck in submitted 1\ understanding transaction status in the transactions page, each transaction has a status (e g , pending, completed, declined, approved, completed, submitted) primevault already shows you the status in the interface if you want to double check on chain, you can click the transaction hash to open it on etherscan (or the relevant block explorer) 2\ when a transaction has failed if the transaction status in primevault is failed , and the block explorer also shows it as failed, you can quickly recreate it without starting from scratch a transaction can fail if gas or tokens are insufficient or the gas fee is set too low steps go to the transactions page find the transaction that was marked as failed (you can double check on the block explorer for the status of the transaction via the transaction hash if the hash is not available, the transaction has failed) click the three dot (…) menu on the right of the row select duplicate review the pre filled details (vault, destination, asset, amount, etc ) what actually happens primevault creates a new transaction with the same parameters a new on chain transaction hash will be created once it’s sent it has its own webhook events and activity log , separate from the original failed attempt think of this as starting a fresh transaction with all the details copied over for convenience 3\ when a transaction is stuck in "submitted" sometimes a transaction is stuck in the submitted state, but it remains in that state for a while (typically due to on chain congestion or a low gas fee) if a transaction has been in the submitted state for around 10–15 minutes , you can safely retry it steps open the transactions page click on the transaction that is in submitted status to open the drawer in the transaction drawer, click retry what “retry” does primevault resends the same transaction with the same nonce (so the new attempt replaces the old pending one), and a higher gas fee , increases the likelihood that miners/validators pick it up quickly no new transaction is created in primevault you still see one transaction in the ui the same webhooks and activity log are used; we’re simply bumping the gas on the existing transaction, not creating a second one think of this as “speeding up” the existing transaction, not creating a duplicate payment