seems the price change much after you halt your computer.
but bots can't update your order when your browser is not acitve, because all code is running in the client side.
so when you open btsbots.com again, the bots update the old orders.
Also the bot seems to refer to the price of the last session under some circumstances:
run bots
new order OPEN.DASH BTS amount: 7.500000000000001 price: 2628.9024795702967
new order OPEN.DASH USD amount: 7.499999999999999 price: 124.16536069244391
run bots
cancel order --- OPEN.DASH BTS
because of price: 2628.9024786666664 change to 1985.2493480088676 ----
new order OPEN.DASH BTS amount: 7.5 price: 1985.2493480088676
cancel order ---- OPEN.DASH USD
because of price: 124.1653601655538 change to 93.76506100000002 -----
new order OPEN.DASH USD amount: 7.5 price: 93.76506100000002
See the price drop from 2629 to 1985 and 124 to 94 just after starting the bot. Bad thing is, orders were given before correction occurs. Nothing happend this time but this could result in huge losses.
Debug info:
Computer was turned off after last session, restarted and reconnected after about 12h, ip should also be a new one.
Hi Alt,
no, I know, so I normally cancel all orders from my wallet after stopping all bots and closing the connection (I reckon closing the tab also closes the active websocket connection). So there were no old orders.
The log I was providing is the log of a just freshly started bot (after complete shutdown of the computer and 12h). The bot gave these orders just after start up and canceled them just after that, when he got a new price. But presumable the old price was saved from the former session and used until new price feeds went in and corrected the situation. Just guessing.
But I can assure you that there were no open orders from the last session when I started the bot. I know from my own experience that users sometimes are confident that a setup was like this or that and rule out any user error. But I'm 100% confident there were no old orders simply because there were no 15 DASH on that account in the last session.
Thanks for looking into this.