Your Message Couldnt Be Retrieved. Please Try Again Later

Sometimes yous may notice yourself facing a problem that doesn't have a clear solution. These troubleshooting tips may help you solve bug you 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 you are swapping.

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

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

one .

Refresh your page and endeavour again later.
2 .

Try trading a smaller amount at in one case.
3 .
Increase your slippage tolerance:
1. ane .
  
  Tap the settings icon on the liquidity page.
2. two .
  
  Increase your slippage tolerance a fiddling and try again.
iv .

Lastly, try inputting an amount with fewer decimal places.

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 pocket-sized-cap token that few people are trading.

However, there'due south also the adventure 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

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

Y'all're trying to add/remove liquidity from a liquidity puddle (LP), but in that location isn't plenty of i of the two tokens in the pair.

Refresh your folio and try again, or attempt again later.

1 .

Tap the settings icon on the liquidity page.
2 .

Increase your slippage tolerance a little and try again.

The fault is acquired by trying to add together or remove liquidity for a liquidity puddle (LP) with an bereft amount of token A or token B (ane of the tokens in the pair).

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

OK, so yous're actually determined to prepare this. Nosotros actually don't recommend doing this unless you know what you're doing.

There currently isn't a simple fashion to solve this issue from the PancakeSwap website: you'll need to interact with the contract directly. You can add together 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 , so Connect to Web3 and connect your wallet.
ii .
In section "1. corroborate", corroborate the LP token for the router past entering
1. 1 .
  
  spender (accost): enter the contract accost of the LP token you're trying to interact with

Query "balanceOf"

2 .

In 5. balanceOf , input your wallet accost and hit Query .
three .

Keep track of the number that's exported. It shows your residual inside the LP in the uint256 format, which you'll demand in the next step.

Add together or Remove Liquidity

1 .

Select Write Contract and Connect to Web3 every bit to a higher place.
2 .

Find addLiquidity or removeLiquidity (whichever one you're trying to exercise)
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" in a higher place.
5 .

Set a depression amountAMin or amountBMin : try ane for both.
half-dozen .

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

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

This tin crusade very loftier slippage, and can cause the user to lose some funds if frontrun

PancakeRouter: EXPIRED

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

Try again, but confirm (sign and circulate) the transaction as presently as y'all generate it.

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

Pancake: Thousand

The transaction cannot succeed due to error: Pancake: M. 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". And then initiate the swap immediately.

This usually happen when you 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.

Brand sure you accept xxx% more than tokens in your wallet than yous intend to trade, or attempt 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 like tDoge or tBTC. Understand how restorative rebase tokens piece of work .

Another possible crusade of this result is the malicious token issuer but 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 yous are trying to swap but failed with this error lawmaking is coming from an airdrop, that is most likely a scam. Delight do non perform any token approving or follow whatsoever links, your fund may be at risk if you try to do then.

Transaction cannot succeed

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

Price Impact likewise High

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

estimateGas failed

This transaction would fail. Please contact back up

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

Please select "Receive WBNB" and retry.

If you lot got this error while trying to swap:

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

This outcome (while swapping) is caused by tokens which have difficult-coded the V1 PancakeSwap router into their contract.

While this practice is ill-brash 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 afflicted volition likely non piece of work with the V2 router: they will almost probable need 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 whatsoever projects which created such tokens should likewise 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 error bulletin is displayed. This error has been reported on mobile devices using Trust Wallet.

1 .

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

If 1. does not resolve your trouble, consider using another wallet such as SafePal for your transaction.

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

The exact details of the problem are still 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 fault message is displayed. This mistake has been reported across platforms.

1 .

Cheque to brand sure yous have sufficient funds available.
two .

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

This fault happens when trading tokens with insufficient allowance, or when a wallet has bereft funds. If you're trading tokens with Restorative Rebase like tau avails tDoge or tBTC, make sure you understand how they work offset with this guide to Rebase tokens .

Issues with Syrup Pools

BEP20: burn down amount exceeds residue

Fail with error 'BEP20: burn down amount exceeds balance'

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

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

1 .

Purchase SYRUP on the commutation. If you desire to unstake 100 CAKE, y'all demand at least 100 SYRUP.

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

ii .

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 whatsoever uncollected Cake yield.

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

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

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

Out of Gas error

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

You have ready 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 ordinarily enough.

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

Basically, your wallet (Metamask, Trust Wallet, etc.) tin't finish what information technology's trying to do.

Your wallet estimates that the gas limit is too depression, so the function phone call runs out of gas before the function call is finished.

BEP20: transfer corporeality exceeds assart

Fail with fault 'BEP20: transfer amount exceeds assart'

1 .

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

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

Endeavour interacting with the contract again.

This happens when y'all ready a limit on your spend allowance when you first approved the contract, and then try to swap more than the limit.

BEP20: transfer amount exceeds balance

Fail with mistake 'BEP20: transfer amount exceeds residue'

You're probably trying to unstake from a Syrup Pool with low rewards in it. Solution below.

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

Firstly, let the squad know which pool you're trying to unstake from, so they can top up the rewards. If you're in a bustle to unstake and you lot don't listen losing your pending yield, try an emergencyWithdraw:

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

1 .

Find the contract address of the Syrup Pool you're trying to unstake from. You tin find it in your wallet's transaction log.
iv .

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

In department "3. emergencyWithdraw", and click "Write".

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

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

This mistake tends to appear when you lot're trying to unstake from an old Syrup Puddle, only there aren't enough rewards in the pool left for you to harvest when withdrawing. This causes the transaction to fail.

Problems with Prediction

Provider Mistake

Provider Error No provider was found

This happens when you lot try to connect via a browser extension similar MetaMask or Binance Chain Wallet, but y'all oasis't installed the extension.

Unsupported Concatenation ID

Switch your chain to BNB Smart Chain. Check your wallet's documentation for a guide if you need help.

Already processing eth_requestAccounts. Please look.

Brand sure you are signed in to your wallet app and information technology's connected to BNB Smart Chain.

Issues buying SAFEMOON and similar tokens

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

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

This is as well why you might non receive every bit much of the token as you look when you buy. Read more than 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 culling wallet.

Internal JSON-RPC mistake. { "code": -32000, "message": "bereft funds for transfer" } - Delight try again.

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

Error: [ethjs-query]

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

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

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

Cause unclear. Try these steps before trying again:

Issues with Contour

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

We're investigating the logic behind this result. Meanwhile please attempt the workaround.

Clear the enshroud and retry.
Retry on different browser.
Retry on different wallet apps.
Retry on the different network (switch between Wi-Fi and cellular)

Checking username keeps spinning

In that location are 2 possible causes.

one .

You take multiple wallets installed on the browser.

Root crusade: You take multiple wallets installed on the browser. It may make a conflict between wallets. This is out of PancakeSwap'due south control and nosotros can do nothing.

1 .

Have merely 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.
two .

Re-type username, and then delight wait for seconds.
three .

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

edneyanstre.blogspot.com

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