πŸš€Troubleshooting

These troubleshooting tips may help you solve problems you might run into.

The transaction cannot succeed due to error: GenesysRouter: INSUFFICIENT_OUTPUT_AMOUNT. This is probably an issue with one of the tokens you are swapping.

the transaction cannot succeed due to error: execution reverted: Genesysrouter: insufficient_output_amount.

You're trying to swap tokens, but your slippage tolerance is too low or liquidity is too low.

Solution:

1-) Refresh your page and try again later.

2-) Try trading a smaller amount at one time.

3-) Increase your slippage tolerance: Tap the settings icon on the liquidity page, Increase your slippage tolerance a little and try again.

4-) Lastly, try inputting an amount with fewer decimal places.

Reasons:

This usually happens when trading tokens with low liquidity.

That means there isn't enough of one of the tokens you're trying to swap in the Liquidity Pool: it's probably a small-cap token that few people are trading.

However, there's also the chance that you're trying to trade a scam token which cannot be sold. In this case, Genesys Network isn't able to block a token or return funds.

INSUFFICIENT_A_AMOUNT or INSUFFICIENT_B_AMOUNT

Fail with error 'GenesysRouter: INSUFFICIENT_A_AMOUNT' or Fail with error 'GenesysRouter: INSUFFICIENT_B_AMOUNT'

You're trying to add/remove liquidity from a liquidity pool (LP), but there isn't enough of one of the two tokens in the pair.

Solution:

Refresh your page and try again, or try again later.

Still doesn't work?

  1. Tap the settings icon on the liquidity page.

  2. Increase your slippage tolerance a little and try again.

Reason:

The error is caused by trying to add or remove liquidity for a liquidity pool (LP) with an insufficient amount of token A or token B (one of the tokens in the pair).

It might be the case that prices are updating too fast when and your slippage tolerance is too low.

The transaction cannot succeed due to error: GenesysRouter: EXPIRED. This is probably an issue with one of the tokens you are swapping.

Try again, but confirm (sign and broadcast) the transaction as soon as you generate it.

This happened because you started making a transaction, but you didn't sign and broadcast it until it was past the deadline. That means you didn't hit "Confirm" quickly enough.

Genesys: K

The transaction cannot succeed due to error: Genesys: K. This is probably an issue with one of the tokens you are swapping.

Try modifying the amount on β€œTo” field. Therefore putting "(estimated)" symbol on β€œFrom”. Then initiate the swap immediately.

This usually happen when you are trying to swap a token with its own fee.

The transaction cannot succeed due to error: execution reverted: Genesys: TRANSFER_FAILED.

Make sure you have 30% more tokens in your wallet than you intend to trade, or try to trade a lower amount. If you want to sell the maximum possible, try 70% or 69% instead of 100%. Caused by the design of Restorative Rebase tokens. Understand how restorative rebase tokens work.

Another possible cause of this issue is the malicious token issuer just suspended the trading for their token. Or they made selling action only possible for selected wallet addresses. Please always do your own research to avoid any potential fraud. If the token you are trying to swap but failed with this error code is coming from an airdrop, that is most likely a scam. Please do not perform any token approval or follow any links, your fund may be at risk if you try to do so.

Try trading a smaller amount, or increase slippage tolerance via the settings icon and try again. This is caused by low liquidity.

Try trading a smaller amount, or increase slippage tolerance via the settings icon and try again. This is caused by low liquidity.

This transaction would fail. Please contact support

If you got this error while removing liquidity from a BNB pair:

Please select "Receive WBNB" and retry.

If you got this error while trying to swap:

Please contact the project team of the token you're trying to swap. **** This issue must be resolved by the project team.

Last updated