If you bridge often and a transfer seems stuck, check its source-chain transaction before sending again. A confirmed deposit may still be waiting to appear on Polygon, while a confirmed withdrawal may need a separate Ethereum step. Retry only after the original transaction failed or you have confirmed it cannot complete.
What should you check first?
Start with the transaction hash, the long string that identifies a transaction on a blockchain explorer. Check it on the chain where you started the transfer: Ethereum for a deposit to Polygon, or Polygon PoS for a withdrawal to Ethereum.
- Failed or reverted: the transaction did not complete on its starting chain. You can submit it again.
- Pending: the starting chain has not confirmed it. Wait; a second transfer could duplicate the first.
- Successful: the starting-chain action completed. Check the next stage before retrying.
“Successful” means the chain accepted that transaction. It does not always mean the tokens have reached the other network. For a deposit, Ethereum tokens are locked and a matching amount is issued on Polygon PoS.
Why can a successful transfer still look stuck?
The two directions finish differently. A deposit from Ethereum is normally relayed to Polygon PoS after the Ethereum transaction succeeds. A withdrawal starts by burning the Polygon version of the token, then requires a checkpoint and an exit transaction on Ethereum.
A checkpoint is a record of Polygon activity that gets submitted to Ethereum. The exit step uses that record to unlock the original tokens. So a withdrawal can be confirmed on Polygon yet still need you to complete the Ethereum side.
For example, if you withdrew 100 USDC and the Polygon transaction succeeded, do not start another 100 USDC withdrawal just because your Ethereum wallet is unchanged. Check whether the withdrawal has reached its checkpoint and whether the exit is ready. The next action may be to finish that withdrawal, not to repeat it.
How do you find the missing stage?
Use the transaction hash and wallet address to match each side of the transfer. Polygon Portal can show transfer activity, and the Polygon Bridge is another way to make the Ethereum-to-Polygon or Polygon-to-Ethereum move. For a confirmed deposit, look for the matching token balance on Polygon PoS; for a withdrawal, check for the Ethereum exit stage.
Check the token as well as the amount. A token with a familiar name can have a different contract address, and bridged tokens may use a different version from a token issued directly on Polygon. Compare the contract address and destination wallet with the transfer details before deciding that funds are missing.
When is it safe to send again?
Retry when the original source transaction is marked failed or reverted, after checking that no matching transfer completed. If it is pending, wait for confirmation. If it succeeded, follow its destination stage to completion; submitting a fresh transfer can move the same funds twice.
For an active routine, save the source hash until you have checked the destination. Confirm the network, token contract, amount, and receiving address before any new transfer. I’d treat the source transaction status as the deciding fact, not a spinner or a balance that has yet to refresh.
In short, identify the direction, check the starting-chain transaction, then resolve the stage it reached. Retry only when that transaction failed; otherwise, complete or wait for the existing transfer.