A stale bridge quote cannot fix a transfer already sent

A stale cross-chain quote can misstate what a new transfer will deliver, but it cannot explain or repair a transfer already sent. The first step is to check whether the source-chain transaction was broadcast and confirmed. A quote is an estimate for a route at a point in time; it is not a live view of funds moving between chains.

Why do cross-chain quotes go stale?

A quote can become outdated because token prices, route liquidity, fees or network conditions changed while the user waited. A bridge aggregator, which compares routes through different bridges and swaps, builds its estimate from the conditions it can see when it is asked. The amount shown on screen may no longer match what a route can provide later.

Some transactions also include a deadline, a time limit after which the contract will reject the instructions. Others may fail for a different reason, such as a changed route or a transaction that no longer meets its minimum output. The wallet prompt is the last chance to review the displayed route and amount before signing. For a fuller walkthrough of route choices, see this guide to bungee bridge. It covers more of the process than this quick explanation.

What should I check if a transfer is stuck?

Check the transaction hash on the source chain first. If the transaction is still pending, the bridge may not have received anything to process. If it failed, the explorer should show that outcome; a new quote may help with a later attempt, but it does not revive the failed one. If it succeeded, look for a bridge status update and any destination-chain transaction.

• Pending: Check the wallet and source-chain explorer. Do not send again until you know whether the first transaction can still confirm.
• Failed: Read the failure details, then decide whether to retry with a fresh quote.
• Confirmed on the source chain: Check the bridge’s status page or tracker using the transaction hash or request ID, if available.
• Marked complete: Check the destination wallet and confirm the token and network. A different token can have a similar name or symbol.

Should I refresh the quote or wait?

Refresh the quote before signing if the displayed route or amount has been sitting for a while. Compare the new output, fees and route details, then make sure the wallet prompt matches what you chose. A higher estimated output can come with a different route or more steps, so the headline amount alone is not enough to compare offers.

After you sign and broadcast the source transaction, refreshing the quote has no effect on it. The bridge must complete the route or report a failure under its own process. If the status has not changed, use the bridge’s stated recovery steps or support channel with the transaction hash; avoid repeating the transfer until you have checked whether the original can still arrive.

The practical rule is simple: quotes help choose a transfer before it is sent; transaction status helps explain one already in motion. Keep the source hash, check each chain involved, and use a fresh quote only for a new attempt.