You Are the One You've Been Waiting for (Internal Family Systems)

Sometimes you may discover yourself facing a problem that doesn't have a articulate solution. These troubleshooting tips may help you solve problems y'all run into.

Issues on the Substitution

INSUFFICIENT_OUTPUT_AMOUNT

The transaction cannot succeed due to error: PancakeRouter: INSUFFICIENT_OUTPUT_AMOUNT. This is probably an result with ane of the tokens y'all are swapping.

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

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

1 .

Refresh your folio and endeavour once more later.
2 .

Effort trading a smaller corporeality at ane fourth dimension.
iii .
Increase your slippage tolerance:
1. 1 .
  
  Tap the settings icon on the liquidity page.
2. 2 .
  
  Increment your slippage tolerance a little and try again.
4 .

Lastly, effort inputting an corporeality with fewer decimal places.

This usually happens when trading tokens with low liquidity.

That ways there isn't enough of ane of the tokens you're trying to swap in the Liquidity Pool: information technology'due south probably a small-cap token that few people are trading.

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

INSUFFICIENT_A_AMOUNT or INSUFFICIENT_B_AMOUNT

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

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

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

i .

Tap the settings icon on the liquidity folio.
2 .

Increase your slippage tolerance a picayune and try again.

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

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

OK, so you're really determined to fix this. Nosotros actually don't recommend doing this unless y'all know what y'all're doing.

In that location currently isn't a simple way to solve this consequence from the PancakeSwap website: y'all'll demand to collaborate with the contract directly. You can add liquidity straight via the Router contract, while setting amountAMin to a pocket-sized corporeality, then withdrawing all liquidity.

Approve the LP contract

one .

Select Write Contract , then Connect to Web3 and connect your wallet.
ii .
In section "1. approve", corroborate the LP token for the router by entering
1. i .
  
  spender (accost): enter the contract accost of the LP token you're trying to interact with

Query "balanceOf"

two .

In v. balanceOf , input your wallet address and striking Query .
three .

Keep runway of the number that'southward exported. It shows your rest inside the LP in the uint256 format, which you lot'll need in the side by side stride.

Add or Remove Liquidity

i .

Select Write Contract and Connect to Web3 as above.
two .

Observe addLiquidity or removeLiquidity (whichever ane you lot're trying to do)
3 .

Enter the token addresses of both of the tokens in the LP.
4 .

In liquidity (uint256), enter the uint256 number which you got from "balanceOf" to a higher place.
5 .

Set a low amountAMin or amountBMin : endeavour 1 for both.
6 .

Add your wallet address in to (address) .
7 .

Deadline must be an epoch fourth dimension greater than the fourth dimension the tx is executed.

This can cause very high slippage, and can cause the user to lose some funds if frontrun

PancakeRouter: EXPIRED

The transaction cannot succeed due to fault: PancakeRouter: EXPIRED. This is probably an upshot with one of the tokens you are swapping.

Try again, simply ostend (sign and broadcast) the transaction as soon as yous generate information technology.

This happened because you lot started making a transaction, only yous didn't sign and broadcast information technology until it was by the deadline. That means you didn't hit "Confirm" speedily plenty.

Pancake: K

The transaction cannot succeed due to fault: Pancake: K. This is probably an outcome with i of the tokens you are swapping.

Endeavour modifying the amount on "To" field. Therefore putting "(estimated)" symbol on "From". Then initiate the swap immediately.

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

Pancake: TRANSFER_FAILED

The transaction cannot succeed due to fault: execution reverted: Pancake: TRANSFER_FAILED.

Make certain 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%. Acquired by the design of Restorative Rebase tokens like tDoge or tBTC. Understand how restorative rebase tokens work .

Another possible cause of this upshot is the malicious token issuer just suspended the trading for their token. Or they made selling activeness only possible for selected wallet addresses. Please e'er do your own research to avoid any potential fraud. If the token y'all are trying to swap merely failed with this error lawmaking is coming from an airdrop, that is about likely a scam. Please do not perform any token approval or follow whatsoever links, your fund may be at risk if yous effort to do so.

Transaction cannot succeed

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

Price Impact too High

Endeavour trading a smaller amount, or increase slippage tolerance via the settings icon and attempt again. This is acquired by low liquidity.

estimateGas failed

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 fault while trying to bandy:

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

This issue (while swapping) is caused by tokens which accept hard-coded the V1 PancakeSwap router into their contract.

While this do is ill-advised at best, the reason for these projects having done this appears to be due to their tokenomics, in which each purchase sends a % of the token to LPs.

The projects affected will likely not work with the V2 router: they will most likely demand to create new versions of their tokens pointing to our new router address, and migrate whatever existing token holders to their new token.

We recommend that any projects which created such tokens should too brand efforts to prevent their users from calculation them to V2 LP.

Cannot read holding 'toHexString' of undefined

"Unknown error: "Cannot read property 'toHexString' of undefined"

When trying to swap tokens, the transaction fails and this error message is displayed. This error has been reported on mobile devices using Trust Wallet.

1 .

Attempt the transaction once more with increased slippage allowance.
2 .

If one. does non resolve your problem, consider using another wallet such as SafePal for your transaction.

This usually happens when trading tokens with bereft slippage assart on Trust Wallet.

The exact details of the problem are even so being investigated.

Execution reverted: TransferHelper: TRANSFER_FROM_FAILED.

The transaction cannot succeed due to error: execution reverted: TransferHelper: TRANSFER_FROM_FAILED.

When trying to swap tokens, the transaction fails and this error message is displayed. This mistake has been reported across platforms.

1 .

Bank check to make sure you have sufficient funds available.
ii .

Ensure yous have given the contract allowance to spend the amount of funds you're attempting to trade with.

This error happens when trading tokens with insufficient allowance, or when a wallet has insufficient funds. If yous're trading tokens with Restorative Rebase like tau assets tDoge or tBTC, make sure yous sympathise how they piece of work first with this guide to Rebase tokens .

Issues with Syrup Pools

BEP20: burn amount exceeds balance

Fail with error 'BEP20: burn amount exceeds remainder'

You lot don't accept enough SYRUP in your wallet to unstake from the CAKE-CAKE pool.

Get at to the lowest degree equally much SYRUP as the corporeality of Cake that you're trying to unstake.

1 .

Purchase SYRUP on the substitution. If yous want to unstake 100 CAKE, yous need at least 100 SYRUP.

If that still fails, y'all can perform an "emergencyWithdraw" from the contract directly to unstake your staked tokens.

2 .

Click "Connect to Web3" and connect your wallet.
3 .

In section "4. emergencyWithdraw" , enter "0" and click "Write".

This will unstake your staked tokens and lose any uncollected CAKE yield.

This will lose any yield that you haven't harvested yet.

To stop this happening once more, don't sell your SYRUP. Yous still demand it to unstake from the "Stake Cake Earn CAKE" pool.

This error has happened considering you have sold or transferred SYRUP tokens. SYRUP is minted in a 1:ane ratio to Cake when you stake in the Block-Cake Syrup Pool. SYRUP must exist burned at a 1:1 ratio to CAKE when calling leaveStaking (unstaking your CAKE from the puddle), and so if you don't have enough, you tin can't unstake from the pool.

Out of Gas mistake

Warning! Error encountered during contract execution [out of gas]

You have set a depression gas limit when trying to make a transaction.

Try manually increasing the gas limit (not gas cost!) in your wallet before signing the transaction.

A limit of 200000 is usually enough.

The above example is from Metamask; check your wallet'south documentation if yous aren't sure how to adapt the gas limit.

Basically, your wallet (Metamask, Trust Wallet, etc.) can't end what it's trying to do.

Your wallet estimates that the gas limit is as well low, and then the function telephone call runs out of gas before the function telephone call is finished.

BEP20: transfer amount exceeds allowance

Fail with error 'BEP20: transfer amount exceeds assart'

1 .

Use Unrekt.net to revoke approval for the smart contract you're trying to interact with
2 .

Corroborate the contract again, without setting a limit on spend allowance
3 .

Try interacting with the contract again.

This happens when yous set a limit on your spend allowance when you first approved the contract, then try to bandy more than than the limit.

BEP20: transfer amount exceeds balance

Neglect with error 'BEP20: transfer amount exceeds balance'

Y'all're probably trying to unstake from a Syrup Puddle with depression rewards in it. Solution below.

If not, you may be trying to send tokens that y'all don't have in your wallet (for case, trying to send a token that is already assigned to a pending transaction). In this case, just make sure you have the tokens you're trying to apply.

Firstly, allow the team know which pool you lot're trying to unstake from, and so they can top upwardly the rewards. If y'all're in a hurry to unstake and you don't mind losing your awaiting yield, try an emergencyWithdraw:

Yous can perform an "emergencyWithdraw" from the contract directly to unstake your staked tokens.

ane .

Find the contract address of the Syrup Puddle you're trying to unstake from. You can find it in your wallet's transaction log.
4 .

Click "Connect to Web3" and connect your wallet.
five .

In section "three. emergencyWithdraw", and click "Write".

This volition unstake your staked tokens and lose any uncollected yield.

This will lose whatsoever yield that you haven't harvested yet.

This error tends to announced when y'all're trying to unstake from an former Syrup Pool, but there aren't enough rewards in the pool left for you to harvest when withdrawing. This causes the transaction to fail.

Bug with Prediction

Other issues

Provider Error

Provider Error No provider was found

This happens when you attempt to connect via a browser extension like MetaMask or Binance Chain Wallet, but you haven't installed the extension.

Unsupported Concatenation ID

Switch your concatenation to BNB Smart Chain. Check your wallet'southward documentation for a guide if y'all need help.

Already processing eth_requestAccounts. Please expect.

Make sure y'all are signed in to your wallet app and it's connected to BNB Smart Chain.

Bug buying SAFEMOON and similar tokens

To trade SAFEMOON, yous must click on the settings icon and set your slippage tolerance to 12% or more than. This is because SafeMoon taxes a 10% fee on each transaction :

five% fee = redistributed to all existing holders
v% fee = used to add liquidity

This is also why you might not receive equally much of the token as you wait when you buy. Read more on How to Buy Safe Moon .

Internal JSON-RPC errors

"MetaMask - RPC Error: Internal JSON-RPC error. estimateGas failed removeLiquidityETHWithPermitSupportingFeeOnTransferTokens estimateGas failed removeLiquidityETHWithPermit "

Happens when trying to remove liquidity on some tokens via Metamask. Root cause is still unknown. Try using an alternative wallet.

Internal JSON-RPC error. { "code": -32000, "bulletin": "insufficient funds for transfer" } - Please try again.

Yous don't have enough BNB to pay for the transaction fees. You lot need more BEP-20 network BNB in your wallet.

Mistake: [ethjs-query]

Error: [ethjs-query] while formatting outputs from RPC '{"value":{"code":-32603,"data":{"code":-32000,"message":"transaction underpriced"}}}"

Increase the gas limit for the transaction in your wallet. Bank check your wallet's documentation to learn how to increment gas limit.

Swap failed: Fault: [ethjs-query] while formatting outputs from RPC '{"value":{"code":-32603,"data":{"code":-32603,"message":"handle request error"}}}'

Cause unclear. Endeavor these steps before trying again:

Issues with Contour

Oops! Nosotros couldn't find any Pancake Collectibles in your wallet.

We're investigating the logic behind this issue. Meanwhile please try the workaround.

Clear the cache and retry.
Retry on different browser.
Retry on dissimilar wallet apps.
Retry on the unlike network (switch betwixt Wi-Fi and cellular)

Checking username keeps spinning

In that location are two possible causes.

one .

You lot have multiple wallets installed on the browser.

Root cause: You have multiple wallets installed on the browser. Information technology may make a disharmonize between wallets. This is out of PancakeSwap's control and we tin can do nothing.

i .

Take only single wallet installed on browser, remove the others.
2 .

Reconnect the wallet and retry setting username again.

Root cause: Network is unstable.

one .

Delete whatever has been entered in the text field completely.
ii .

Re-type username, then please wait for seconds.
iii .

If information technology doesn't piece of work, reload the page and retry again.

johnsontrece1938.blogspot.com

Source: https://docs.pancakeswap.finance/help/troubleshooting