When a Cross-Chain Transfer Times Out, What Happens Next?

When a cross-chain transfer times out, the result depends on whether the bridge’s deposit expired or only its status tracker stopped waiting. A source-chain transaction can already be final while the destination transfer is still pending, so “timed out” alone does not show where the funds are.

Some bridges set a deadline for a relayer to deliver funds; others use different message or claim steps. For Across, an unfilled deposit can become eligible for a refund after its fill deadline, but the refund follows a separate settlement process. A timeout is a status to investigate, not proof that funds are lost or already on their way back.

Does a timeout mean the transfer failed?

Not necessarily: a timeout in a wallet or website may only mean its tracker stopped receiving updates. Check the source transaction on the source-chain explorer first; if it is confirmed, the deposit may be held by the bridge even though the destination wallet has not received anything.

Then check the bridge’s own status page or tracker using the source transaction hash, and look for a destination transaction. If the destination transaction exists but is pending or failed, that is a different problem from a deposit that no relayer has filled. For background on expected timing in a particular flow, see Acrossbridge treasury transfer wait times.

What happens when the bridge deadline expires?

A bridge-specific deadline usually marks the point when an unfilled deposit can move into another process; it does not make every bridge transfer reverse automatically. On Across, a deposit that reaches its fill deadline without a relayer fill can become eligible for a refund, provided no partial fill was executed.

The refund is not an instant reversal of the original transaction. Across documents describe the expired deposit being included in settlement, then a refund being sent to the designated refund address after the relevant processing and cross-chain steps. That means the return can take hours, and the refund address may be different from the wallet that initiated the transfer.

Status terms can help distinguish the stages:

• Pending: the deposit is waiting for a fill; it has not necessarily expired.
• Expired: the fill deadline has passed and, on Across, a refund may be entering its processing path.
• Refunded: the return transaction has completed; check the address and chain shown in the status details.

What should you check before trying again?

Start with the source transaction hash, not a second transfer. Confirm the source-chain transaction succeeded, compare the amount and recipient with the bridge record, and check whether the destination chain shows a fill or a failed execution.

If the bridge reports an expired or refund-pending status, wait for its stated refund process and verify which address is set to receive the funds. If the status remains unclear, give support the source hash and bridge status; do not assume that sending the same amount again will replace the first deposit.

Retrying can be reasonable once the first transfer is confirmed refunded or the bridge establishes that it never received the deposit. Until then, the practical choice is to track the existing transfer across both chains, since the visible timeout may describe the tracker rather than the funds.