Swaps fail for predictable reasons like slippage, low liquidity, expired quotes, approvals, or congestion. Learn quick fixes and how to prevent failures.
TL;DR
The most common swap failure is slippage: the price moved outside your tolerance before your transaction executed.
Other frequent causes include low liquidity, expired quotes, missing approvals, congestion, and incorrect network or token settings.
Wallets like MetaMask and major platforms highlight slippage and price movement as top reasons.
In most cases, a failed swap does not mean your tokens were “taken.” It means the trade did not execute as intended. Depending on the chain and what happened, you might still pay some network cost.
Swap Failure Troubleshooting at a Glance
Before diving into each failure type, here’s a quick troubleshooting table you can scan in seconds. If your swap failed, find the closest match below, apply the fix, then read the detailed section for context.
Failure reason | What it usually means | What to do now | What to watch out for |
|---|---|---|---|
Slippage tolerance too low | The price moved beyond your allowed range before execution | Increase slippage slightly, reduce trade size, retry when volatility cools | Setting slippage too high can lead to much worse execution |
Low liquidity | The pool could not absorb your trade size without pushing price too far | Swap a smaller amount, choose a more liquid pair, try another route | Thin pools often cause poor pricing even if the swap succeeds |
Quote expired | The quoted route or price was only valid for a short time and expired before confirmation | Refresh the quote and confirm faster | This is especially common in crosschain swaps |
Network congestion or bad gas settings | Your transaction was delayed, stayed pending, or became uncompetitive | Wait for calmer conditions, then retry; resolve stuck pending transactions first | Delays can turn into slippage or quote-expiry failures |
Not enough fee balance | You did not have the right native gas token or enough balance for the full route | Make sure you have enough gas for the chain, and for crosschain routes check both ends | Some wallets and bridges need gas on the destination chain too |
Missing or failed token approval | The swap contract was not allowed to spend your token | Complete the approval first, then retry the swap | Previous approvals may be insufficient and need to be redone |
Problematic token | The token may have taxes, transfer restrictions, blacklist logic, or poor support | Verify the contract address and check route support before trying again | If it looks like a scam token, stop instead of retrying blindly |
RPC or app issue | The infrastructure or wallet app itself had a temporary problem | Wait briefly, restart the app, and update to the latest version | Sometimes the issue is technical plumbing, not the swap itself |
Unsupported network or mode | The feature, route, or swap type is not available on that chain or in that setting | Switch to a supported network or use another route | Double-check chain selection before retrying |
If your wallet shows the swap failed, your next job is simple: identify which failure class it was, then apply the right fix.
The 9 most common reasons swaps fail (and what to do)
1) Slippage tolerance was too low
Low slippage tolerance is the #1 reason across many wallets: your quoted price changed before execution, and the swap aborted to protect you. How to fix:
Increase slippage slightly (small steps).
Try a smaller amount.
Avoid swapping during sudden volatility spikes.
When to be careful: If you crank slippage too high, you might get a much worse execution. Higher slippage is not a free fix.
2) Liquidity was too thin for your trade size
If a pool is shallow, your trade moves the price too much. Some routes cannot fill your size at your minimum received, so they fail. How to fix:
Reduce trade size.
Choose a more liquid pair (often via USDC, ETH, WETH).
Try a different route or aggregator.
3) Quote expired (especially common in crosschain swaps)
Many swaps rely on quotes that are only valid for a short window. If you confirm late, or the network is slow, the quote can expire. How to fix:
Refresh the quote.
Confirm faster after reviewing details.
If the network is busy, wait and try again later.
This is why “Expiry passed” shows up in swap troubleshooting pages and help centers.
4) Network congestion or gas settings caused delay
If the network is congested and your transaction is underpriced for current conditions, it can sit pending. While it waits, price and quotes change, and your swap can fail. How to fix:
Retry when the network is calmer.
If you have a stuck pending transaction, resolve that first (speed up, cancel, or replace, depending on wallet and chain).
5) You did not have the right fee balance for the route
On some wallets, you need the native gas token. On crosschain routes, you might need gas on the destination chain too. That is a common failure point. How to fix:
Ensure the route can cover gas on both ends.
Use a wallet experience that reduces native gas dependency when possible.
walllet.com’s swap guide explicitly calls out this friction and designs around it by removing the need to hold the native gas token for swap execution in its flow.
6) Token approval was missing or failed
Many ERC-20 swaps require an approval before the swap can spend your token. If the approval fails, or you never completed it, the swap fails. How to fix:
Approve first, then swap.
If you previously approved, you might need to re-approve after changes, or if allowance is insufficient.
If approvals make you nervous, learn how allowances work and how to revoke them later.
7) The token is “problematic” (taxed, rebasing, blacklisted, or unsupported)
Some tokens have transfer fees or restrictions. Some are not supported by certain routes. Some are scam tokens that cannot be sold. How to fix:
Verify the token contract address.
Check if the token is supported by your route/provider.
If you suspect a scam token, stop. Do not throw more transactions at it.
8) RPC or app issues (yes, sometimes it’s just the plumbing)
Sometimes the backend node you are connected to is unstable, or the app needs an update. Coinbase’s swap troubleshooting, for example, recommends waiting and retrying, and ensuring the app is updated. How to fix:
Wait 60 seconds and retry.
Restart the app.
Update the wallet to the latest version.
9) You are trying to swap on an unsupported network or mode
Some swap features only work on certain networks, or need a specific setting enabled. How to fix:
Confirm the network supports the swap feature you are using.
Switch to a supported network, or use a different route.
A fast “diagnosis” flow you can follow
If you want one simple routine: Read the error message. It usually hints at slippage, quote expiry, or gas. Check slippage and minimum received. If it is tight, adjust slightly. Check trade size. If big, try smaller. Refresh quote and confirm promptly. Confirm approvals are done. If the network is congested, wait.
How to prevent swap failures next time
You do not need to be a DeFi expert. You need good defaults. Use minimum received as your truth, not a chart screenshot. Prefer liquid tokens and routes. Avoid swapping during extreme volatility. Keep your wallet updated. For crosschain: plan for destination chain conditions too.
How Where walllet.com makes Swaps easy & smart
Your swap can fail for many reasons, but two pain points show up constantly:
gas token dependency
unclear confirmations
walllet.com’s swap flow is designed to reduce gas token dead-ends and keep the swap experience more “product-like” than “toolbox-like,” which lowers the chance of beginner failures. Open walllet.com, refresh your quote, check minimum received, and retry with a slightly higher slippage or smaller size if needed.
