You can tell whether to wait, retry or seek a recovery by checking which stage the swap reached. The right next step depends on whether the source-chain transaction confirmed and whether the destination-chain action completed. A cross-chain swap can involve a source swap, a bridge transfer and a destination swap, so one “pending” label may hide different stages. When you are ready to plan a new attempt, Rango Bridge can help find a route across networks; first, check the status of the attempt already in flight.
What does the status actually mean?
Start with the source transaction hash in the source chain’s block explorer. A submitted transaction that is still pending has not yet been included in a block; one marked failed was included but its execution reverted. In either case, the bridge may not have received any tokens.
- Source pending: the source-chain transaction is not confirmed.
- Source confirmed: the first transaction succeeded, but later steps may remain.
- Destination pending: the bridge transfer arrived or is being processed, but the final swap or delivery may not be done.
- Failed or timed out: a step reported an error, or a protocol timeout may have started a recovery path.
Source pending. Check the transaction’s block confirmations and nonce, the sequence number a wallet uses for your account’s transactions. If the transaction remains unconfirmed, a later transaction with the same nonce may replace it on some EVM chains; only do this if you understand the wallet’s replacement behavior. Do not start a second cross-chain swap just because the first looks slow.
Source confirmed. A confirmed source transaction proves that its on-chain action ran; it does not prove you received the destination token. Look for a destination transaction or transfer record using the route’s transaction details. For example, if an illustrative swap sends 0.10 ETH and the source explorer shows success but the destination explorer shows no transaction yet, the bridge or relayer may still be processing the handoff.
Destination pending. Some routes need another transaction after the bridge transfer, such as a swap into the requested token. On IBC routes, packets carry data between chains, and an acknowledgement reports success or an error; a timeout can trigger a separate recovery process. These steps can lag behind the source confirmation, so check the destination chain and route status before acting.
What should you do next?
Match the action to the last verified step. If the source transaction failed, confirm whether tokens remain in your wallet before retrying. If it succeeded but the destination step is missing, keep the hash and check the route’s status or recovery instructions; do not assume the funds are lost or send a duplicate. If the destination transaction failed, verify whether the route returned funds or requires a recovery action.
Use this short checklist: confirm the source hash; identify the last successful step; check the destination chain for receipt; follow the route’s stated recovery path if it reports failure; retry only after you know what happened to the original amount. I use the same sequence when checking a Rango Bridge attempt: transaction evidence first, then any route-specific recovery step.