Read the error first
Open the failed transaction on a block explorer. Jupiter's common-errors page maps the codes below.
| Error | Meaning | What to change |
|---|---|---|
| 6001 SlippageToleranceExceeded | Price moved between quote and landing | Raise slippage or use dynamic slippage, then send faster |
| Transaction expired | The blockhash expired before landing | Re-quote and send faster |
| NO_ROUTES_FOUND | No liquidity path | Check the token's markets and liquidity |
| 6024 InsufficientFunds | Not enough tokens for the swap, fees or rent | Check balances before quoting |
| "Some routes failed to load" | Usually RPC problems | Change the RPC in settings, refresh and retry |
Slippage and speed
Too tight a slippage setting makes swaps fail, too loose loses value. Jupiter's support guidance says a very volatile token may take a few attempts, usually no more than 3. Any delay between getting a quote and sending the swap lets the price move outside your tolerance. Read what slippage is.
Landing the transaction
Jupiter lists these factors: a competitive priority fee, an accurate compute-unit amount, sensible slippage and efficient broadcasting. Its docs recommend using dynamic compute-unit limits, dynamic slippage and a priority fee together.
Providers
A slow RPC causes expiry and loading failures, see the RPC providers page and what an RPC is. More on Jupiter.