Your Invitation Has Expired. Search on to Try Again Later

Sometimes you may find yourself facing a trouble that doesn't have a clear solution. These troubleshooting tips may assist you solve problems yous meet.

Problems 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 lot are swapping.

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

You're trying to swap tokens, only your slippage tolerance is besides low or liquidity is besides low.

one .

Refresh your page and try again later.
2 .

Try trading a smaller amount at one time.
three .
Increase your slippage tolerance:
1. 1 .
  
  Tap the settings icon on the liquidity folio.
2. ii .
  
  Increase your slippage tolerance a little and try once more.
4 .

Lastly, try inputting an amount with fewer decimal places.

This normally happens when trading tokens with low liquidity.

That means there isn't enough of one of the tokens you lot're trying to swap in the Liquidity Pool: information technology's probably a minor-cap token that few people are trading.

However, in that location's too the chance that you're trying to trade a scam token which cannot be sold. In this example, 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'

Y'all're trying to add/remove liquidity from a liquidity puddle (LP), but there isn't enough of one of the two tokens in the pair.

Refresh your page and endeavor over again, or endeavour over again later.

1 .

Tap the settings icon on the liquidity page.
2 .

Increase your slippage tolerance a little and endeavour again.

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

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

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

There currently isn't a simple way to solve this issue from the PancakeSwap website: yous'll demand to interact with the contract straight. You lot tin can add liquidity directly via the Router contract, while setting amountAMin to a pocket-size amount, then withdrawing all liquidity.

Approve the LP contract

1 .

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

Query "balanceOf"

ii .

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

Proceed track of the number that'southward exported. It shows your balance within the LP in the uint256 format, which you'll need in the side by side step.

Add or Remove Liquidity

1 .

Select Write Contract and Connect to Web3 as above.
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.
four .

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

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

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

Borderline must be an epoch fourth dimension greater than the time 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 error: PancakeRouter: EXPIRED. This is probably an event with 1 of the tokens you are swapping.

Try again, just confirm (sign and broadcast) the transaction every bit shortly equally you generate it.

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

Pancake: M

The transaction cannot succeed due to error: Pancake: K. This is probably an issue with ane 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 usually 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.

Make sure you accept 30% more than tokens in your wallet than you 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%. Acquired past the pattern of Restorative Rebase tokens similar tDoge or tBTC. Understand 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 activeness but possible for selected wallet addresses. Please always do your ain inquiry to avoid any potential fraud. If the token you are trying to swap but failed with this mistake code is coming from an airdrop, that is nearly likely a scam. Please do not perform any token approving or follow any links, your fund may be at risk if you attempt to exercise so.

Transaction cannot succeed

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

Price Touch on likewise High

Attempt trading a smaller amount, or increment slippage tolerance via the settings icon and try again. This is acquired past low liquidity.

estimateGas failed

This transaction would fail. Please contact support

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

Delight select "Receive WBNB" and retry.

If you got this error while trying to bandy:

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

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

While this do is ill-advised at all-time, 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 volition probable not work with the V2 router: they will well-nigh likely need to create new versions of their tokens pointing to our new router accost, and drift whatever 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 belongings 'toHexString' of undefined

"Unknown mistake: "Cannot read holding 'toHexString' of undefined"

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

i .

Effort the transaction over again with increased slippage allowance.
two .

If 1. does not resolve your problem, consider using another wallet such every bit SafePal for your transaction.

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

The verbal 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 mistake message is displayed. This fault has been reported across platforms.

ane .

Cheque to make sure you accept sufficient funds available.
2 .

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

This mistake happens when trading tokens with insufficient allowance, or when a wallet has insufficient funds. If you're trading tokens with Restorative Rebase similar tau assets tDoge or tBTC, make sure you understand how they work beginning with this guide to Rebase tokens .

Problems with Syrup Pools

BEP20: burn amount exceeds balance

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

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

Get at to the lowest degree as much SYRUP as the amount of CAKE that you're trying to unstake.

1 .

Buy SYRUP on the exchange. If you want to unstake 100 CAKE, yous need at to the lowest degree 100 SYRUP.

If that even so fails, you 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 volition lose whatsoever yield that you haven't harvested yet.

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

This error has happened because you accept sold or transferred SYRUP tokens. SYRUP is minted in a 1:1 ratio to Block when yous stake in the Block-Block Syrup Pool. SYRUP must be burned at a i:1 ratio to CAKE when calling leaveStaking (unstaking your CAKE from the pool), and so if you don't take enough, you lot tin can't unstake from the pool.

Out of Gas error

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

Yous have set a low gas limit when trying to make a transaction.

Endeavour 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's documentation if you aren't certain how to adjust the gas limit.

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

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

BEP20: transfer amount exceeds allowance

Neglect with mistake 'BEP20: transfer amount exceeds assart'

one .

Apply Unrekt.net to revoke approval for the smart contract yous're trying to interact with
ii .

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

Endeavour interacting with the contract again.

This happens when you lot set a limit on your spend allowance when you starting time canonical the contract, so endeavour to swap more than the limit.

BEP20: transfer amount exceeds rest

Neglect with error 'BEP20: transfer amount exceeds balance'

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

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

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

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

1 .

Observe the contract accost of the Syrup Pool you're trying to unstake from. You lot can find it in your wallet'south transaction log.
4 .

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

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

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

This will lose whatever yield that y'all haven't harvested nonetheless.

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

Issues with Prediction

Other bug

Provider Error

Provider Error No provider was plant

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

Unsupported Concatenation ID

Switch your concatenation to BNB Smart Concatenation. Cheque your wallet'due south documentation for a guide if yous need aid.

Already processing eth_requestAccounts. Please wait.

Make sure you are signed in to your wallet app and it's continued to BNB Smart Concatenation.

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 :

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

This is likewise why you might not receive as much of the token every bit you wait when you lot purchase. Read more on How to Buy Safe Moon .

Internal JSON-RPC errors

"MetaMask - RPC Fault: 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. Endeavor using an alternative wallet.

Internal JSON-RPC error. { "code": -32000, "message": "bereft funds for transfer" } - Please try over again.

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

Error: [ethjs-query]

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

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

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

Cause unclear. Effort these steps before trying once again:

Problems with Profile

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

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

Clear the cache and retry.
Retry on unlike 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 two possible causes.

i .

Yous have multiple wallets installed on the browser.

Root crusade: Y'all take multiple wallets installed on the browser. It may make a conflict betwixt wallets. This is out of PancakeSwap'due south control and we tin 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.

1 .

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

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

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

martinezcoultoy.blogspot.com

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