Why a SyncSwap Swap Fails: A Practical Troubleshooting Checklist
A failed SyncSwap swap usually comes from one of five checks: the wrong network, no native gas token, missing token approval, insufficient liquidity, or a slippage limit the market could not meet. The correct fix depends on where the process stopped. A quote that never appears is different from a signed transaction that reverts, and neither problem should be solved by blindly increasing slippage. Identify the failure stage before trying again.
First identify whether the quote or transaction failed
If no estimated output appears, the problem occurred before a transaction was submitted. Check that the wallet is connected to the intended network, the input token is held on that network, and the amount is entered in the correct asset. A token on one chain can have the same symbol and address format as a token elsewhere while remaining unusable for the selected route.
If the wallet rejected the request, read the rejection message rather than submitting repeatedly. A missing approval, insufficient balance, or inadequate gas balance can prevent the transaction from being created. For an ERC-20 token, approval is commonly a separate transaction that authorizes a contract to spend the chosen amount. The approval must be confirmed before the swap can use those tokens.
If a transaction hash exists but the result is marked failed or reverted, the network received the request but the contract’s conditions were not met. That is a different situation from a wallet connection problem.
A missing quote usually points to the network, token, or route
Start with the least risky checks. Confirm the network shown in the wallet, compare the token contract address with the source you trust, and make sure the wallet holds enough of the input token for the intended amount. Leave room for gas in the network’s native asset; holding only the token being sold may not be enough to submit an approval or swap.
If the pair still cannot be priced, the route may lack usable liquidity, the token may not be supported by the available pools, or the amount may be too large for the pool’s reserves. Reducing the trade size is a useful diagnostic: if a small amount produces a quote but the original amount does not, the issue is likely route depth or price impact rather than the wallet.
If the network or token context is unclear, use SyncSwap to confirm the current SyncSwap context for the selected network and pair before retrying. That check does not establish that a token is safe or liquid, so verify the contract address and examine the quoted price impact separately.
A reverted swap needs a controlled retry
Two figures matter here: price impact and slippage tolerance. Price impact is the estimated effect of your trade size on the pool price. Slippage tolerance is the amount of movement you allow between the quote and execution. Increasing slippage does not reduce price impact; it only permits execution at a worse rate.
Use this decision rule:
- If the quoted price impact is already unacceptable, reduce the amount or divide the trade into smaller transactions.
- If price impact is acceptable but the swap fails because the market moved, refresh the quote and use a modestly wider tolerance only if the possible loss is acceptable.
- If the token has transfer restrictions, a fee-on-transfer mechanism, or unusual contract behavior, changing slippage may not solve the failure.
Before signing again, compare the minimum received amount with the result you are willing to accept. A transaction that reverts normally leaves the input asset in the wallet, but the wallet may still show a gas charge for the failed attempt. Check the transaction record and balance rather than assuming the swap completed.
A pending transaction requires a different response
Do not submit another swap immediately while the first one is pending. First check whether the transaction is visible on the explorer for the selected network. If there is no matching record, the wallet may not have broadcast it successfully. If there is a record, inspect its status and nonce.
A pending transaction can block later transactions from the same wallet because EVM transactions are processed in nonce order. Sending several replacements may create confusion and can result in an unintended execution once the network accepts one of them. Use the wallet’s documented replacement or cancellation process only after confirming the original transaction’s status.
Retry only after the checklist passes
Before the next attempt, confirm the network, token address, input balance, native gas balance, approval status, quoted output, price impact, minimum received amount, and transaction nonce. Test with a smaller amount if the original trade was large relative to available liquidity. If the same error appears after those checks, preserve the exact message and transaction status; repeating the transaction without new information increases cost without identifying the cause.