Alpaca Finance
Search…
English
Our Protocol
Automated Vaults
AUSD
Tokenomics
Join the Herd (AlpaCareers)
Resources
⚠️ Common Error Messages
Below are some common error messages you might see in the block explorer for your failed transactions and how to fix them
Error Messages
Explanation of what happened
Solutions
ERC20: transfer amount exceeds allowance
You have previously set a limit on how much Alpaca's smart contract can move your token, which is lower than the amount your are now trying to execute.
- It's also a good practice revoke any previously allowance on contracts you no longer plan to use in the future for security purpose.
Vault::work:: bad work factor
Debt ratio is higher than the allowed leveraged. This normally happens when you try to add collateral to your active position but the amount is not enough to bring the position value below allowed leveraged. More explanation here
Another scenario would be if a user try to open large position relative to the pool's liquidity which cause his position to immediately goes below the allowed work factor (through price impact caused from opening a position.) If you are not a whale, don't worry about this one. :)
- Increase the amount of collateral you are adding
- Reduce your position size
Vault::work:: insufficient funds in the vault
Not enough liquidity in the deposit vault for the loan size that you requested
- Reduce your position size
- Wait for utilization level of the pool to reduce
Vault::work:: too small debt size
The debt size you are requesting is too small. Please refer to this table for the minimum allowed debt size for each asset.
- Increase amount of supplied asset
- Increase leverage
Insufficient LP tokens received
Your transaction was reverted because there is a large, unfavorable price movement beyond your slippage settings before the transaction is confirmed
- Increase slippage tolerance but make sure that it is not too high
- Refresh page and try again
Insufficient farming tokens received
Your transaction was reverted because there is a large, unfavorable price movement beyond your slippage settings before the transaction is confirmed
- Increase slippage tolerance but make sure that it is not too high
- Refresh page and try again
Insufficient baseToken received
Your transaction was reverted because there is a large, unfavorable price movement beyond your slippage settings before the transaction is confirmed
- Increase slippage tolerance but make sure that it is not too high
- Refresh page and try again
WorkerConfig::isStable:: price too high
Asset price on PCS is 10%+ higher than the price from our external price oracle. Read more about how this protect you from bad prices here
- Wait a bit until the price on PCS and external feed converge (update every ~15 minutes)
BigNumber
One of the parameters your tx tried to pass was larger than what's accepted in the smart contract. When this error occurs, often, it's because you accidentally confirmed a duplicate tx for the same action, such as a deposit or withdrawal. Due to the funds already having moved, there's usually insufficient funds for a 2nd tx.
Another common reason to see this is if slippage for an LYF position is too high.
- If it's an issue of repeat txs, check if your intended tx already went through. If so, you can ignore this error and continue with what you were doing.
- If it's a slippage issue, If trying to open/close a position, you can avoid slippage by opening/closing your position without fees using this guide: https://docs.alpacafinance.org/alpaca-academy/lesson-4-open-close-positions-with-0-swap-feesOr you can increase your slippage settings on the top right of the app using the Gear icon.
- If it's for another issue, refresh page and try again.
WorkerConfig::isStable:: price too low
Asset price on PCS is 10%+ lower than the price from our external price oracle. Read more about how this protect you from bad prices here
- Wait a bit until the price on PCS and external feed converge (update every ~15 minutes)
Last modified 5mo ago
Copy link