Amazon Missed Delivery Says Theyll Try Again Later What Does That Mean

Sometimes y'all may notice yourself facing a trouble that doesn't take a articulate solution. These troubleshooting tips may help yous solve problems you come across.

Issues on the Exchange

INSUFFICIENT_OUTPUT_AMOUNT

The transaction cannot succeed due to fault: PancakeRouter: INSUFFICIENT_OUTPUT_AMOUNT. This is probably an consequence 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 swap tokens, but your slippage tolerance is too depression or liquidity is too low.

ane .

Refresh your folio and try once again later.
ii .

Attempt trading a smaller amount at i time.
three .
Increment your slippage tolerance:
1. one .
  
  Tap the settings icon on the liquidity page.
2. ii .
  
  Increase your slippage tolerance a little and attempt again.
4 .

Lastly, try inputting an corporeality with fewer decimal places.

This usually happens when trading tokens with low liquidity.

That means in that location isn't enough of ane of the tokens you're trying to swap in the Liquidity Pool: it'due south probably a small-cap token that few people are trading.

All the same, there's likewise the run a risk that you're trying to trade a scam token which cannot be sold. In this case, PancakeSwap isn't able to cake a token or render funds.

INSUFFICIENT_A_AMOUNT or INSUFFICIENT_B_AMOUNT

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

You lot're trying to add/remove liquidity from a liquidity puddle (LP), simply there isn't enough of one of the ii tokens in the pair.

Refresh your page and try again, or attempt again afterwards.

1 .

Tap the settings icon on the liquidity page.
2 .

Increase your slippage tolerance a little and endeavour again.

The error is acquired past trying to add or remove liquidity for a liquidity pool (LP) with an bereft amount of token A or token B (one 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're really determined to fix this. We really don't recommend doing this unless yous know what yous're doing.

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

Approve the LP contract

ane .

Select Write Contract , and so Connect to Web3 and connect your wallet.
2 .
In section "1. approve", approve the LP token for the router by inbound
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 address and hit Query .
3 .

Keep track of the number that'southward exported. It shows your remainder within the LP in the uint256 format, which you'll need in the next step.

Add or Remove Liquidity

1 .

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

Detect addLiquidity or removeLiquidity (whichever ane y'all're trying to do)
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" above.
v .

Set a low amountAMin or amountBMin : try 1 for both.
half-dozen .

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

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

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

PancakeRouter: EXPIRED

The transaction cannot succeed due to mistake: PancakeRouter: EXPIRED. This is probably an issue with one of the tokens yous are swapping.

Try again, but ostend (sign and circulate) the transaction as shortly equally y'all generate it.

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

Pancake: K

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

Endeavor modifying the amount on "To" field. Therefore putting "(estimated)" symbol on "From". So initiate the swap immediately.

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

Pancake: TRANSFER_FAILED

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

Brand sure yous have 30% more tokens in your wallet than you lot intend to trade, or try to trade a lower amount. If you desire to sell the maximum possible, try lxx% or 69% instead of 100%. Caused 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 just suspended the trading for their token. Or they made selling action just possible for selected wallet addresses. Please e'er do your own research to avoid whatsoever potential fraud. If the token you are trying to swap simply failed with this mistake code is coming from an airdrop, that is virtually likely a scam. Please do not perform any token approving or follow whatsoever links, your fund may be at gamble if you try to exercise then.

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 too High

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

estimateGas failed

This transaction would neglect. Please contact support

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

Please select "Receive WBNB" and retry.

If yous got this fault while trying to swap:

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

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

While this practise is sick-brash at all-time, the reason for these projects having washed 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 will most likely need to create new versions of their tokens pointing to our new router address, and migrate whatsoever existing token holders to their new token.

We recommend that any projects which created such tokens should also make efforts to forestall their users from calculation them to V2 LP.

Cannot read belongings 'toHexString' of undefined

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

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

one .

Attempt the transaction again with increased slippage allowance.
2 .

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

This usually happens when trading tokens with bereft slippage allowance on Trust Wallet.

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

i .

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

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

This error happens when trading tokens with bereft 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 empathise how they work showtime with this guide to Rebase tokens .

Bug with Syrup Pools

BEP20: burn corporeality exceeds residual

Fail with error 'BEP20: burn amount exceeds balance'

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

Get at least as much SYRUP equally the amount of CAKE that yous're trying to unstake.

1 .

Buy SYRUP on the substitution. If you want to unstake 100 CAKE, you need at least 100 SYRUP.

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

2 .

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

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

This volition unstake your staked tokens and lose whatever uncollected CAKE yield.

This will lose whatever yield that you haven't harvested all the same.

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

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

Out of Gas error

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

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

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

A limit of 200000 is usually enough.

The in a higher place case is from Metamask; bank check your wallet's documentation if you aren't sure how to adjust the gas limit.

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

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

BEP20: transfer amount exceeds allowance

Fail with error 'BEP20: transfer amount exceeds allowance'

1 .

Apply Unrekt.net to revoke approval for the smart contract you're trying to collaborate with
2 .

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

Try interacting with the contract once again.

This happens when you set a limit on your spend assart when you first canonical the contract, and then endeavour to swap more than the limit.

BEP20: transfer amount exceeds remainder

Fail with error 'BEP20: transfer corporeality exceeds balance'

Y'all're probably trying to unstake from a Syrup Puddle with low rewards in it. 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, just make certain yous have the tokens you're trying to employ.

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

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

i .

Detect the contract address of the Syrup Pool yous're trying to unstake from. You can find it in your wallet'south transaction log.
4 .

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

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

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

This will lose any yield that yous haven't harvested however.

This error tends to announced when you're trying to unstake from an one-time Syrup Pool, simply 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 issues

Provider Error

Provider Error No provider was found

This happens when you lot endeavour to connect via a browser extension like MetaMask or Binance Chain Wallet, merely you lot haven't installed the extension.

Unsupported Chain ID

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

Already processing eth_requestAccounts. Delight wait.

Brand certain you are signed in to your wallet app and it'southward continued to BNB Smart Chain.

Issues buying SAFEMOON and like tokens

To merchandise SAFEMOON, you must click on the settings icon and ready 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
five% fee = used to add liquidity

This is too why you might non receive as much of the token as you await when yous purchase. Read more than on How to Buy 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 yet unknown. Try using an alternative wallet.

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

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

Error: [ethjs-query]

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

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

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

Cause unclear. Try these steps before trying once again:

Issues with Contour

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

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

Clear the cache 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 ii possible causes.

i .

You accept multiple wallets installed on the browser.

Root cause: You have multiple wallets installed on the browser. It may make a disharmonize betwixt wallets. This is out of PancakeSwap's control and we can exercise nothing.

ane .

Have only unmarried wallet installed on browser, remove the others.
two .

Reconnect the wallet and retry setting username once again.

Root cause: Network is unstable.

1 .

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

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

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

jordanopinkh.blogspot.com

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