Getting error - `Non-200 status code: '429'` while trying to switch Matic to USDC.e.
Zartaj0 opened this issue · comments
I am playing around with Aave, have 10 Matic supplied on polygon chain. Now I want to switch those Matics to USDC.e. But the moment I try to do so, I get this warning on Metamask:
And then if I continue with executing the tx, I get this error pop up on the AAVE frontend:
On copying the error message I got this - Non-200 status code: '429'
- Windows 10
- Browser Brave
EDIT: After disabling Blockaid, I tried switching again, and spent the gas fees on a reverted transaction, digging into the transaction, I found the point of error.
As of now I withdrew and supplied, but would like to read the code and know the reason for this error.
I was just about to post the same error regarding Aave Polygon. I've been having it with different transactions. The main one is that I can't withdraw my Matic. This has been happening for the last 3 weeks. All my positions are hostage on Aave Polygon. One time I was miraculously able to withdraw in the middle of all the errors I got.
Error is the same as above: Non-200 status code: '429'
I've gotten this error consistently like 50 times total for the last 3 weeks. I cannot withdraw any token.
Please someone fix this or give us a workaround.
I've found a workaround that seems to work for me at least - turning off blockaid in settings (three dots, settings, - security & Privacy
I've found a workaround that seems to work for me at least - turning off blockaid in settings (three dots, settings, - security & Privacy
I don't think this is a solution, because blockaid is just used to simulate the transaction and make sure that there won't be any error in the mainnet execution.
I anyways tried it and TX got reverted because of less amount, now I am digging into the contracts.
Same error (Non-200 status code: '429') today while trying to switch from DAI to USDC or USDC.e in Polygon v3; Metamask on Android, both with the built in browser and with Chrome.
I've found a workaround that seems to work for me at least - turning off blockaid in settings (three dots, settings, - security & Privacy
I don't think this is a solution, because blockaid is just used to simulate the transaction and make sure that there won't be any error in the mainnet execution.
I anyways tried it and TX got reverted because of less amount, now I am digging into the contracts.
Just tested this after posting my previous comment, and the transaction actually went through. Blockaid is doing more than just checking and advising it seems. That can be seen as either weird or fishy. :-\
Just tested this after posting my previous comment, and the transaction actually went through. Blockaid is doing more than just checking and advising it seems. That can be seen as either weird or fishy. :-\
weird, didn't work for me, I manually had to withdraw, swap, supply :(
@Zartaj0 the Received amount of tokens are less than expected error can happen if your slippage is set too low. But in this case it should have shown an error in the UI modal, and not let you submit the tx. I can try to investigate a little and see if I can reproduce.
@vonwao when you are trying to withdraw your Matic, what amount are you setting for the approval? If you are using metamask, they allow you to override the requested approval amount and set it to your wallet balance. However, if you do this, the transaction will fail because your Matic supply will have increased (from earned apy) by the time you go to withdraw, so the approval will no longer be enough.
@Zartaj0 the
Received amount of tokens are less than expectederror can happen if your slippage is set too low. But in this case it should have shown an error in the UI modal, and not let you submit the tx. I can try to investigate a little and see if I can reproduce.
Thanks for replying @grothem, I saw this point somewhere earlier, so I tried to increase the slippage, and tried all of the available options, 0.1%, 0.5%, and 1%. But I got the same popup.
Also about submitting the transaction, the only time it got submitted was when I disabled Blockaid on Metamask, before that I was only receiving that popup.