Hi Guys,
I'm new to GB and i've gotten GB 3.3.2 running on Bittrex exchange for about a day.
Once I've stopped it properly while putting in a buy manually in the market suggested by the bot selling price.
Later when i've restarted GB I kept seeing this error on the screen which wasnt there earlier...
at console.C:\snapshot\Users\Enrico\Desktop\xBot_v2.9.3\bittrex.js.module.exports.Market.checkifwesold.Promise.bittrex.private.getOpenOrders.then (evalmachine.<anonymous>:0:0)
Exchange: 'BTC-ETH',
at tryCatcher (C:\snapshot\Users\Enrico\Desktop\xBot_v2.9.3\node_modules\bluebird\js\release\util.js:16:23)
OrderType: 'LIMIT_SELL',
at Promise._settlePromiseFromHandler (C:\snapshot\Users\Enrico\Desktop\xBot_v2.9.3\node_modules\bluebird\js\release\promise.js:512:31)
Quantity: 0.14572218,
at Promise._settlePromise (C:\snapshot\Users\Enrico\Desktop\xBot_v2.9.3\node_modules\bluebird\js\release\promise.js:569:18)
QuantityRemaining: 0.14572218,
at Promise._settlePromise0 (C:\snapshot\Users\Enrico\Desktop\xBot_v2.9.3\node_modules\bluebird\js\release\promise.js:614:10)
Limit: 0.0693723,
at Promise._settlePromises (C:\snapshot\Users\Enrico\Desktop\xBot_v2.9.3\node_modules\bluebird\js\release\promise.js:693:18)
CommissionPaid: 0,
at Async._drainQueue (C:\snapshot\Users\Enrico\Desktop\xBot_v2.9.3\node_modules\bluebird\js\release\async.js:133:16)
Price: 0,
at Async._drainQueues (C:\snapshot\Users\Enrico\Desktop\xBot_v2.9.3\node_modules\bluebird\js\release\async.js:143:10)
PricePerUnit: null,
at Immediate.Async.drainQueues (C:\snapshot\Users\Enrico\Desktop\xBot_v2.9.3\node_modules\bluebird\js\release\async.js:17:14)
Opened: '2017-10-05T13:43:55.057',
at runCallback (timers.js:651:20)
Closed: null,
at tryOnImmediate (timers.js:624:5)
CancelInitiated: false,
at processImmediate [as _immediateCallback] (timers.js:596:5)
ImmediateOrCancel: false,
IsConditional: false,
Condition: 'NONE',
ConditionTarget: null } ]
Could you guys give me some pointers as to what has gone wrong here. Nothing in the configs were changed and I've seen some posts on someone having this issue before but not sure how it was resolved.