Try Again Enter Your Answer Using Dimensions of Chemical Concentration.

Sometimes you may detect yourself facing a problem that doesn't have a clear solution. These troubleshooting tips may help you lot solve problems you lot run into.

Issues on the Exchange

INSUFFICIENT_OUTPUT_AMOUNT

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

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

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

1 .

Refresh your page and try over again later.
2 .

Try trading a smaller amount at in one case.
3 .
Increase your slippage tolerance:
1. 1 .
  
  Tap the settings icon on the liquidity folio.
2. two .
  
  Increment your slippage tolerance a little and effort again.
four .

Lastly, try inputting an amount with fewer decimal places.

This normally happens when trading tokens with low liquidity.

That ways there isn't enough of i 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 likewise the chance that you're trying to trade a scam token which cannot exist sold. In this case, PancakeSwap isn't able to block a token or return funds.

INSUFFICIENT_A_AMOUNT or INSUFFICIENT_B_AMOUNT

Fail with mistake 'PancakeRouter: INSUFFICIENT_A_AMOUNT' or Fail with fault 'PancakeRouter: INSUFFICIENT_B_AMOUNT'

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

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

one .

Tap the settings icon on the liquidity folio.
ii .

Increase your slippage tolerance a trivial and try again.

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

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

OK, so you lot're really determined to set up this. We really don't recommend doing this unless you know what you're doing.

There currently isn't a uncomplicated fashion to solve this result from the PancakeSwap website: yous'll need to interact with the contract directly. You lot tin can add liquidity directly via the Router contract, while setting amountAMin to a small amount, and so withdrawing all liquidity.

Approve the LP contract

1 .

Select Write Contract , then Connect to Web3 and connect your wallet.
2 .
In section "one. approve", approve the LP token for the router past entering
1. 1 .
  
  spender (address): enter the contract accost of the LP token yous're trying to interact with

Query "balanceOf"

two .

In five. balanceOf , input your wallet address and hit Query .
three .

Go on rail of the number that's exported. Information technology shows your balance within the LP in the uint256 format, which y'all'll demand in the adjacent pace.

Add or Remove Liquidity

1 .

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

Observe addLiquidity or removeLiquidity (whichever i yous're trying to practice)
3 .

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

In liquidity (uint256), enter the uint256 number which yous got from "balanceOf" above.
five .

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

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

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

This can cause very loftier 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 issue with one of the tokens yous are swapping.

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

This happened because you started making a transaction, only you didn't sign and broadcast information technology until it was past the borderline. That means you lot didn't hit "Confirm" chop-chop enough.

Pancake: Chiliad

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

Endeavour modifying the corporeality on "To" field. Therefore putting "(estimated)" symbol on "From". And so initiate the swap immediately.

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

Pancake: TRANSFER_FAILED

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

Make certain you have xxx% more tokens in your wallet than yous intend to merchandise, or attempt to trade a lower amount. If y'all want to sell the maximum possible, try seventy% or 69% instead of 100%. Caused by the pattern of Restorative Rebase tokens like tDoge or tBTC. Sympathise how restorative rebase tokens work .

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

Transaction cannot succeed

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

Toll Touch on also Loftier

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

estimateGas failed

This transaction would neglect. Delight contact back up

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 team.

This issue (while swapping) is acquired past tokens which have hard-coded the V1 PancakeSwap router into their contract.

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

The projects affected will likely not work with the V2 router: they volition almost likely need to create new versions of their tokens pointing to our new router address, and drift any existing token holders to their new token.

We recommend that any projects which created such tokens should as well make efforts to prevent their users from adding them to V2 LP.

Cannot read property 'toHexString' of undefined

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

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

one .

Attempt the transaction over again with increased slippage allowance.
2 .

If ane. does not resolve your problem, consider using some other wallet such as SafePal for your transaction.

This normally happens when trading tokens with insufficient slippage allowance 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 bandy tokens, the transaction fails and this error message is displayed. This fault has been reported across platforms.

ane .

Check to make sure you have sufficient funds bachelor.
two .

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

This fault happens when trading tokens with bereft assart, or when a wallet has bereft funds. If you're trading tokens with Restorative Rebase like tau assets tDoge or tBTC, make sure you sympathise how they work first with this guide to Rebase tokens .

Issues with Syrup Pools

BEP20: burn amount exceeds balance

Fail with error 'BEP20: burn amount exceeds balance'

You don't have enough SYRUP in your wallet to unstake from the Cake-Cake pool.

Get at least as much SYRUP every bit the amount of CAKE that you're trying to unstake.

1 .

Buy SYRUP on the exchange. If y'all want to unstake 100 Block, you need at to the lowest degree 100 SYRUP.

If that nonetheless fails, you tin perform an "emergencyWithdraw" from the contract directly to unstake your staked tokens.

2 .

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

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

This will unstake your staked tokens and lose whatever uncollected Block yield.

This volition lose any yield that you oasis't harvested however.

To cease this happening again, don't sell your SYRUP. You notwithstanding need it to unstake from the "Stake Block Earn CAKE" pool.

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

Out of Gas mistake

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

You take set a low gas limit when trying to make a transaction.

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

A limit of 200000 is usually enough.

The above example is from Metamask; check your wallet'southward documentation if you aren't certain how to adjust the gas limit.

Basically, your wallet (Metamask, Trust Wallet, etc.) tin can't terminate what it's trying to practice.

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

BEP20: transfer amount exceeds allowance

Fail with mistake 'BEP20: transfer amount exceeds assart'

1 .

Apply Unrekt.cyberspace to revoke approving for the smart contract you're trying to interact with
2 .

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

Try interacting with the contract again.

This happens when you lot set a limit on your spend allowance when you kickoff approved the contract, and then endeavour to swap more than the limit.

BEP20: transfer amount exceeds residuum

Neglect with error 'BEP20: transfer amount exceeds residuum'

You're probably trying to unstake from a Syrup Pool with depression rewards in information technology. Solution below.

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

Firstly, let the team know which puddle you're trying to unstake from, so they can top upwards the rewards. If you're in a hurry to unstake and you lot don't listen losing your pending yield, effort an emergencyWithdraw:

You can perform an "emergencyWithdraw" from the contract straight to unstake your staked tokens.

one .

Find the contract accost 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 "3. emergencyWithdraw", and click "Write".

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

This will lose any yield that y'all haven't harvested notwithstanding.

This fault tends to announced when you're trying to unstake from an quondam Syrup Puddle, merely there aren't enough rewards in the pool left for you to harvest when withdrawing. This causes the transaction to fail.

Problems with Prediction

Other bug

Provider Error

Provider Mistake No provider was constitute

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

Unsupported Concatenation ID

Switch your chain to BNB Smart Concatenation. Bank check your wallet's documentation for a guide if yous need help.

Already processing eth_requestAccounts. Delight await.

Brand sure yous are signed in to your wallet app and it's connected to BNB Smart Concatenation.

Issues buying SAFEMOON and similar tokens

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

5% fee = redistributed to all existing holders
5% fee = used to add liquidity

This is too why you might non receive as much of the token every bit you expect when you purchase. Read more on How to Buy Safety Moon .

Internal JSON-RPC errors

"MetaMask - RPC Mistake: Internal JSON-RPC mistake. estimateGas failed removeLiquidityETHWithPermitSupportingFeeOnTransferTokens estimateGas failed removeLiquidityETHWithPermit "

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

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

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

Error: [ethjs-query]

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

Increment the gas limit for the transaction in your wallet. Check your wallet's documentation to learn how to increase gas limit.

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

Crusade unclear. Try these steps earlier trying again:

Problems with Profile

Oops! We couldn't find whatsoever 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 unlike browser.
Retry on different wallet apps.
Retry on the dissimilar network (switch between Wi-Fi and cellular)

Checking username keeps spinning

There are two possible causes.

1 .

You take multiple wallets installed on the browser.

Root cause: You have multiple wallets installed on the browser. It may make a disharmonize between wallets. This is out of PancakeSwap's command and we can practice null.

ane .

Have just single wallet installed on browser, remove the others.
2 .

Reconnect the wallet and retry setting username again.

Root cause: Network is unstable.

i .

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

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

If it doesn't work, reload the page and retry once more.

Try Again Enter Your Answer Using Dimensions of Chemical Concentration.

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

eye makeup