When Should You Claim a Failed Bridge Transfer Manually?

Should you claim a bridge transfer manually or wait for the relayer? If the source transaction succeeded and the transfer is ready to redeem, wait briefly for an automatic retry; claim manually when retries stop or you need to submit the destination transaction yourself. Neither option sends the source transfer again: both aim to complete its unfinished destination leg.

What does a relayer retry do?

A relayer watches for a bridge message and submits the redemption transaction on the destination chain. In a Wormhole Token Bridge transfer, that message is represented by a Guardian-signed Verifiable Action Approval, or VAA; redemption uses it to release native tokens from custody or mint the corresponding wrapped asset. A retry resubmits that destination action after a failed or delayed attempt.

Check the source transaction first: if it reverted, there is no successful transfer for a relayer to complete. If it succeeded, check whether the required attestation is available and whether a destination redemption has already succeeded. The fuller portal bridge guide explains the claim flow in more detail.

What changes when you claim manually?

A manual claim has you, or the app that initiated the transfer, submit the redemption transaction on the destination chain. You need the source transaction hash to find the transfer, and your wallet must be able to sign for the relevant destination address. You also pay the destination chain’s transaction fee.

Manual submission can help when the relayer is unavailable or repeated attempts have not completed the transfer. It cannot skip missing attestation, fix a failed source transaction, or redirect funds to a different recipient. Some transfer routes restrict who may redeem, so use the original app if the bridge interface cannot complete the claim.

How do you decide whether to wait or claim?

For most readers, give an active relayer a short chance to retry, then claim manually once the proof is ready and no destination redemption is recorded. Before signing, match the source hash, destination chain and recipient to the transfer you intended. Use the same route that initiated it if redemption is restricted.

• Source transaction failed: stop; there is no transfer to redeem.
• Attestation pending: wait for it before trying a claim.
• Attestation ready, no redemption: retry or submit the manual claim.
• Redemption succeeded: check the destination wallet and token; do not claim again.

A successful redemption is recorded on the destination chain, and replay protection prevents the same bridge message from paying out twice. Your next check is the destination transaction status: once it confirms, verify the recipient and token before treating the transfer as complete.