Skip to main content

Common Errors

In this section, you can find the list of errors that can be returned by the Jupiter Swap API, Swap Program or from other programs like DEXes, System or Token programs.

Program Errors

Jupiter Swap Program Errors

Jupiter Swap Program IDL
Abnormal Error Rates

If you face high or consistent amounts of errors, please reach out to Jupiter Discord.

Error CodeError NameDebug
6001SlippageToleranceExceededTry higher fixed slippage or try dynamicSlippage
6008NotEnoughAccountKeysLikely modified swap transaction causing missing account keys
6014IncorrectTokenProgramIDLikely attempted to take platform fees on a Token2022 token (This is also 0x177e)
6017ExactOutAmountNotMatchedSimilar to slippage

Solana Program Errors

ProgramLink
Token Programhttps://github.com/solana-program/token/blob/main/program/src/error.rs
Token2022 Programhttps://github.com/solana-program/token-2022/blob/main/program/src/error.rs
Associated Token Account Programhttps://github.com/solana-program/associated-token-account/blob/main/program/src/error.rs
Other Solana Programshttps://github.com/solana-program

DEX Program Errors

In the swap transaction, the DEX in routing may return errors. You can find some of their IDLs and/or error codes in an explorer. If they do not support public IDLs or open source code, you can reference the common errors below or if you need additional help, please reach out to Jupiter Discord.

ErrorDescription
Error related to tick array or bitmap extension accountSimilar to slippage, the price or market has "moved out of range", hence the swap transaction failed.

Routing Errors

The common routing errors you may encounter are usually related to attempting to swap a token that is not tradable on Jupiter, for reasons such as lack of liquidity or the token is not supported.

ErrorDescriptionDebug
NO_ROUTES_FOUNDNo routes were found for the requested swap
COULD_NOT_FIND_ANY_ROUTEUnable to find any valid route for the swap
ROUTE_PLAN_DOES_NOT_
CONSUME_ALL_THE_AMOUNT
The calculated route cannot process the entire input amount, you can get more output amount by reducing your input amount
  • Try reducing your input amount
MARKET_NOT_FOUNDThe specified market address was not found
  • Verify the market address exists and is active
TOKEN_NOT_TRADABLEThe specified token mint is not available for trading
NOT_SUPPORTEDGeneric error for unsupported operations
  • Check the specific error message for details
CIRCULAR_ARBITRAGE_
IS_DISABLED
Attempted to swap a token for itself
  • Input and output tokens must be different
CANNOT_COMPUTE_
OTHER_AMOUNT_THRESHOLD
Failed to calculate the minimum output amount based on slippage
  • Verify the input amount and slippage parameters are valid

Swap Transaction Composing Errors

ErrorDescriptionDebug
MAX_ACCOUNT_GREATER_THAN_MAXThe specified number of accounts exceeds the maximum allowed
  • Reduce the number of accounts in the transaction
INVALID_COMPUTE_UNIT_PRICE_AND_PRIORITIZATION_FEEBoth compute unit price and prioritization fee were specified
  • Use either compute unit price or prioritization fee, not both
FAILED_TO_GET_SWAP_AND_ACCOUNT_METASFailed to generate the swap transaction
  • Check the error message for specific details

Best Practices

It is important to understand the error codes when your products are user facing. This will help you provide a better experience for your users, helping them make an informed decision or follow up step to help their transaction succeed.

Jup.ag as a reference

You can use https://jup.ag/ as a reference to understand how we handle errors on the UI.

Error TypeBest Practice
Slippage exceeding thresholdShow the user the current slippage tolerance and the incurred slippage
Insufficient fundsShow the user the current balance of the account and the required balance
Non Jupiter Program ErrorsAllow the user to retry with a different route and/or exclude the specific DEX from the quote request
Token not tradableShow the user the token is not tradable and provide context on why it's not tradable