-
Notifications
You must be signed in to change notification settings - Fork 2k
Different Bittrex error #659
Comments
I get some similiar error when trading ETH-BTC on bittrex too. It crashes the zenbot sometimes. When I restart zenbot after that, it doesn't lead to reproducable termination of the zenbot though. I can provide the error message and anything else that might be required (just let me know): |
This a different error. My error crashes the bot and only happens after many hours of trading, while your's allows the bot to continue. Your's is the same as #280 I believe. |
got the same error today, already fixed the previous error with fix from #457 |
@luponata My bad. Are you trading with BTC-USDT as well as other coin-BTC pairs? I have a feeling that might be what caused the problem. |
@brucetus i'm only using SNT-BTC, still testing! |
Same here. If anybody has mod permissions can you please delete @ether-btc comment because it is addressed in a different issue and is taking up huge amounts of space. |
I think I have solved the problem. It appears that every once in a while the Bittrex API will choke and not return a result. I'm not sure how this impacts checking for orders or if the result from Bittrex is undefined, then do not process any trades. It isn't the best case since no new trades will be pulled in, but it will prevent the bot from crashing till the site is available again. Since I cannot force Bittrex to fail, I have no way to legitimately test this. |
This is a proposed fix for "Different Bittrex error DeviaVir#659".
I got another one of these errors with the fix in place. I was worried that since it wasn't able to be duplicated due to a problem at Bittrex, this would happen again. |
This fix should handle any error that happens and then fire's off a retry. I tried the Try .. Catch block on fiddle and it worked flawlessly to capture the error in question. I'm not sure how to exactly test the retry, but I created the statement similar to the one on line 78. This technically should be recoverable, because Bittrex is just having some sort of hiccup on their API sending data.
Thanks KryptoNova you're a hero. |
* Different Bittrex error (#659) This fix should handle any error that happens and then fire's off a retry. I tried the Try .. Catch block on fiddle and it worked flawlessly to capture the error in question. I'm not sure how to exactly test the retry, but I created the statement similar to the one on line 78. This technically should be recoverable, because Bittrex is just having some sort of hiccup on their API sending data. * Needed to pass an object instead of a string.
I already used the fix in #457 and it worked for a couple days. However, I got a new error that occured after selling.
The sell order already printed too and it said 'sold' for about 10 minutes before I got the error.
The text was updated successfully, but these errors were encountered: