When to Retry a Cross-Chain Swap

A cross-chain swap can look stalled while its source transaction is already confirmed and its destination transfer is still processing. Check both sides before resubmitting, because a new swap may move funds a second time.

• Source pending: the transaction has not yet settled on the chain where it began.
• Source failed: the transaction reverted or was dropped; check the wallet and swap interface for the result.
• Source confirmed, destination pending: the swap began, but its cross-chain message or destination action has not completed.
• Destination failed: the source may have completed while the final action needs recovery or a supported retry.

How can you tell whether a swap is actually stuck?

Start with the source transaction hash in the relevant chain explorer or the swap interface. A pending status means the source chain has not confirmed it; a confirmed status means the next step is to check the destination status.

Cross-chain systems often pass a message between chains after the source transaction settles. That handoff can take longer than the wallet’s confirmation, so a quiet destination does not by itself mean the swap failed.

For route selection after a stall, see this guide to choosing a quickswap route after a stall. First establish whether the source transaction succeeded; route advice cannot settle that question.

When should you wait instead of resubmitting?

Wait when the source transaction is pending or confirmed and the destination remains in progress. Keep the transaction hash, note the displayed status, and use the swap interface’s own recovery path if it offers one.

Do not submit another swap just because the first one has not appeared on the destination. If the first transfer completes later, the second submission can create a separate swap with its own price, fees, and outcome.

When is it reasonable to submit again?

Resubmit only after the original attempt is confirmed failed or the interface explicitly says it did not start. Check whether funds returned to the source wallet and whether the protocol provides a recovery or retry action for that transaction.

A wallet’s speed-up or cancellation option applies to some pending transactions on some chains. It is not a universal bridge retry, and replacing a pending source transaction does not replay a destination message that was already sent.

What should you check before retrying?

Use the same transaction record to distinguish a delayed handoff from a failed swap. If the status is ambiguous, wait for clearer confirmation or contact the protocol’s support with the transaction hash rather than sending the funds again.

For most users, the safer default is to wait while the original transaction is pending or the destination is processing. Retry only when the original attempt is clearly failed or the protocol directs recovery for that specific transaction.