Your Submission Did Not Succeed Please Try Again Linkedin

Sometimes you lot may find yourself facing a trouble that doesn't take a articulate solution. These troubleshooting tips may help you solve problems you run across.

Issues on the Exchange

INSUFFICIENT_OUTPUT_AMOUNT

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

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

Y'all're trying to swap tokens, simply your slippage tolerance is too low or liquidity is besides low.

1 .

Refresh your folio and endeavor over again later.
2 .

Try trading a smaller amount at once.
3 .
Increase your slippage tolerance:
1. 1 .
  
  Tap the settings icon on the liquidity page.
2. 2 .
  
  Increment your slippage tolerance a little and endeavour again.
iv .

Lastly, endeavor inputting an corporeality with fewer decimal places.

This usually happens when trading tokens with depression liquidity.

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

However, there's also the gamble that you lot'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 fault 'PancakeRouter: INSUFFICIENT_A_AMOUNT' or Fail with fault 'PancakeRouter: INSUFFICIENT_B_AMOUNT'

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

Refresh your folio and try again, or try again subsequently.

1 .

Tap the settings icon on the liquidity page.
2 .

Increase your slippage tolerance a piddling and endeavour again.

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

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

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

At that place currently isn't a simple way to solve this issue from the PancakeSwap website: you'll need to interact with the contract directly. You lot can add liquidity directly via the Router contract, while setting amountAMin to a small amount, so withdrawing all liquidity.

Approve the LP contract

one .

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

Query "balanceOf"

2 .

In v. balanceOf , input your wallet address and hitting Query .
3 .

Keep runway of the number that'south exported. It shows your residuum within the LP in the uint256 format, which you'll need in the next pace.

Add or Remove Liquidity

1 .

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

Notice addLiquidity or removeLiquidity (whichever one you're trying to do)
iii .

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

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

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

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

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

This tin can cause very loftier slippage, and tin 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 event with one of the tokens you are swapping.

Effort once more, just confirm (sign and broadcast) the transaction as soon equally yous generate it.

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

Pancake: K

The transaction cannot succeed due to error: Pancake: K. This is probably an result with i of the tokens yous are swapping.

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

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

Pancake: TRANSFER_FAILED

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

Brand sure you take 30% more tokens in your wallet than you intend to trade, or endeavor to trade a lower amount. If you want to sell the maximum possible, endeavour seventy% or 69% instead of 100%. Caused past the pattern of Restorative Rebase tokens like tDoge or tBTC. Understand how restorative rebase tokens work .

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

Transaction cannot succeed

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

Price Impact likewise Loftier

Endeavour trading a smaller amount, or increment slippage tolerance via the settings icon and endeavor again. This is caused past 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 swap:

Please contact the project team of the token yous're trying to swap. **** This effect must exist resolved by the projection team.

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

While this practice 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 non work with the V2 router: they will nearly likely demand to create new versions of their tokens pointing to our new router address, and migrate any existing token holders to their new token.

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

Cannot read property 'toHexString' of undefined

"Unknown fault: "Cannot read holding '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.

one .

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

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

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

The exact details of the problem are nevertheless beingness 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 bulletin is displayed. This error has been reported across platforms.

1 .

Check to brand certain you have sufficient funds bachelor.
2 .

Ensure yous accept given the contract assart 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 bereft funds. If you're trading tokens with Restorative Rebase like tau assets tDoge or tBTC, make certain yous understand how they work first with this guide to Rebase tokens .

Issues with Syrup Pools

BEP20: fire amount exceeds residual

Neglect with error 'BEP20: burn amount exceeds remainder'

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

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

1 .

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

If that still fails, you lot tin 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 end this happening once again, don't sell your SYRUP. Yous still need information technology to unstake from the "Stake Cake Earn CAKE" pool.

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

Out of Gas mistake

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

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

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

A limit of 200000 is usually plenty.

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

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

Your wallet estimates that the gas limit is too low, so the role call runs out of gas earlier the office call is finished.

BEP20: transfer corporeality exceeds assart

Fail with error 'BEP20: transfer amount exceeds allowance'

1 .

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

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

Try interacting with the contract over again.

This happens when yous set up a limit on your spend assart when you get-go canonical the contract, then try to swap more the limit.

BEP20: transfer amount exceeds residuum

Fail with fault 'BEP20: transfer corporeality exceeds balance'

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

If not, you lot may exist trying to send tokens that you don't have in your wallet (for instance, trying to send a token that is already assigned to a pending transaction). In this case, just brand sure you have the tokens you're trying to use.

Firstly, permit the team know which puddle you're trying to unstake from, and so they can top up the rewards. If you're in a hurry to unstake and you don't listen losing your awaiting yield, try an emergencyWithdraw:

Y'all can perform an "emergencyWithdraw" from the contract directly to unstake your staked tokens.

1 .

Detect the contract accost of the Syrup Pool you're trying to unstake from. You can discover 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 whatever uncollected yield.

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

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

Issues with Prediction

Provider Error

Provider Mistake No provider was found

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

Unsupported Chain ID

Switch your chain to BNB Smart Chain. Bank check your wallet'southward documentation for a guide if y'all need assistance.

Already processing eth_requestAccounts. Please wait.

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

Issues buying SAFEMOON and like tokens

To trade SAFEMOON, you lot 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 :

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

This is also why you might not receive as much of the token as you expect when y'all buy. Read more on How to Buy Prophylactic 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 error. { "code": -32000, "message": "bereft funds for transfer" } - Please try again.

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

Fault: [ethjs-query]

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

Increase 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"}}}'

Cause unclear. Endeavor these steps before trying again:

Bug with Contour

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

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

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

Checking username keeps spinning

There are two possible causes.

1 .

You lot have 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'due south control and nosotros can practice nothing.

1 .

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

Reconnect the wallet and retry setting username once more.

Root cause: Network is unstable.

1 .

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

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

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

millerspoself.blogspot.com

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