Chance to Work Again on Amazon After a Termination

Sometimes y'all may find yourself facing a trouble that doesn't have a articulate solution. These troubleshooting tips may help yous solve problems yous see.

Issues on the Exchange

INSUFFICIENT_OUTPUT_AMOUNT

The transaction cannot succeed due to fault: PancakeRouter: INSUFFICIENT_OUTPUT_AMOUNT. This is probably an issue with 1 of the tokens yous 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.

1 .

Refresh your page and effort again later.
2 .

Endeavor trading a smaller amount at one time.
3 .
Increase your slippage tolerance:
1. 1 .
  
  Tap the settings icon on the liquidity page.
2. 2 .
  
  Increase your slippage tolerance a petty and try again.
4 .

Lastly, try inputting an amount with fewer decimal places.

This ordinarily happens when trading tokens with low liquidity.

That means 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.

Nonetheless, at that place's as well the chance that you're trying to merchandise 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 fault 'PancakeRouter: INSUFFICIENT_B_AMOUNT'

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

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

ane .

Tap the settings icon on the liquidity page.
2 .

Increment your slippage tolerance a picayune and attempt again.

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

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

OK, and then you're really determined to fix this. We actually don't recommend doing this unless you lot know what you're doing.

There currently isn't a simple style to solve this event from the PancakeSwap website: you'll need to interact with the contract directly. You can add liquidity straight via the Router contract, while setting amountAMin to a pocket-size amount, and then withdrawing all liquidity.

Approve the LP contract

1 .

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

Query "balanceOf"

two .

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

Keep rails of the number that's exported. It shows your remainder within the LP in the uint256 format, which you'll demand in the adjacent pace.

Add or Remove Liquidity

1 .

Select Write Contract and Connect to Web3 as in a higher place.
2 .

Discover addLiquidity or removeLiquidity (whichever one you'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 y'all got from "balanceOf" in a higher place.
five .

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

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

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

This can crusade very high slippage, and can crusade 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 ane of the tokens y'all are swapping.

Effort once more, simply ostend (sign and broadcast) the transaction every bit soon as you generate information technology.

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

Pancake: Thousand

The transaction cannot succeed due to error: Pancake: Thousand. 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 bandy 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 error: execution reverted: Pancake: TRANSFER_FAILED.

Brand certain you accept 30% more tokens in your wallet than yous intend to merchandise, or endeavor to merchandise a lower amount. If you want to sell the maximum possible, endeavour 70% or 69% instead of 100%. Caused by the blueprint of Restorative Rebase tokens like tDoge or tBTC. Empathize how restorative rebase tokens work .

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

Transaction cannot succeed

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

Price Impact as well Loftier

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

estimateGas failed

This transaction would fail. Please contact back up

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

Delight select "Receive WBNB" and retry.

If yous got this error while trying to swap:

Delight contact the project team of the token you lot're trying to swap. **** This result must exist resolved by the project team.

This issue (while swapping) is caused past 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 not work with the V2 router: they will nigh likely demand to create new versions of their tokens pointing to our new router accost, and drift any existing token holders to their new token.

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

Cannot read belongings 'toHexString' of undefined

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

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

one .

Attempt the transaction again with increased slippage allowance.
2 .

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

This usually happens when trading tokens with insufficient slippage allowance 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 error message is displayed. This error has been reported across platforms.

1 .

Check to brand sure you lot have sufficient funds available.
2 .

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

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

Issues with Syrup Pools

BEP20: burn down amount exceeds balance

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

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

Get at least as much SYRUP as the corporeality of CAKE that y'all're trying to unstake.

1 .

Purchase SYRUP on the exchange. If you want to unstake 100 CAKE, you demand at least 100 SYRUP.

If that notwithstanding fails, y'all can perform an "emergencyWithdraw" from the contract straight 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 any uncollected Block yield.

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

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

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

Out of Gas fault

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

You have 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 commonly plenty.

The above instance is from Metamask; check your wallet's documentation if you aren't sure how to adjust the gas limit.

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

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

BEP20: transfer amount exceeds allowance

Fail with error 'BEP20: transfer amount exceeds allowance'

1 .

Utilise Unrekt.cyberspace to revoke approval for the smart contract you're trying to interact with
two .

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

Effort interacting with the contract once more.

This happens when yous fix a limit on your spend assart when y'all kickoff approved the contract, then try to bandy more than the limit.

BEP20: transfer amount exceeds rest

Fail with error 'BEP20: transfer amount exceeds balance'

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

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

Firstly, let the squad know which pool you're trying to unstake from, and then they tin top upward the rewards. If you're in a hurry to unstake and you don't mind losing your pending yield, effort an emergencyWithdraw:

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

one .

Notice the contract address of the Syrup Pool y'all're trying to unstake from. Yous can notice it in your wallet's transaction log.
four .

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

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

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

This will lose any yield that yous oasis't harvested yet.

This fault tends to appear when you're trying to unstake from an erstwhile Syrup Pool, merely at that place aren't enough rewards in the pool left for you to harvest when withdrawing. This causes the transaction to fail.

Issues with Prediction

Other issues

Provider Error

Provider Mistake No provider was found

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

Unsupported Chain ID

Switch your chain to BNB Smart Concatenation. Check your wallet'due south documentation for a guide if yous demand help.

Already processing eth_requestAccounts. Please wait.

Brand sure y'all are signed in to your wallet app and it'south continued to BNB Smart Chain.

Issues buying SAFEMOON and like tokens

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

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

This is as well why you lot might not receive equally much of the token as you expect when you purchase. Read more than on How to Purchase Safe Moon .

Internal JSON-RPC errors

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

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

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

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

Error: [ethjs-query]

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

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

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

Crusade unclear. Try these steps before trying again:

Issues with Profile

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

Checking username keeps spinning

There are two possible causes.

1 .

You have multiple wallets installed on the browser.

Root crusade: You have multiple wallets installed on the browser. It may brand a conflict betwixt wallets. This is out of PancakeSwap'due south command and we tin practise nothing.

1 .

Have merely unmarried wallet installed on browser, remove the others.
ii .

Reconnect the wallet and retry setting username again.

Root cause: Network is unstable.

1 .

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

Re-type username, and then delight expect for seconds.
iii .

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

rembertmolon1997.blogspot.com

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