The combo bot 6790cd63ab6a336e8254f9f7 force-liquidated the position, while there was still balance on the account. I received a notification as welll about liquidation.
Last deals:
But as I mentioned, the account had free USDT balance, so I don’t understand what caused the bot to think it’s out of funds and liquidate the deal.
Thank you for your report regarding the liquidation issue with the combo bot (ID: 6790cd63ab6a336e8254f9f7) on KuCoin Future. We understand this can be frustrating, especially when there was still a balance on your account.
We have received your message and will investigate the matter further. If you have a specific deal ID related to this liquidation, please provide it to help us expedite our review. We will update you shortly.
Does the liquidation not happened in the exchange?
Those messages are auto generated by the exchange. Bot doesn’t liquidate itself.
Hmm… Well, yes, the Exchange does show forced liquidation, but I don’t understand why. THe uPNL is -6.25 USDT only, and the account has funds.
One thing I see that exchange is showing that position is “Isolated” long, but my bot is using “Cross”:
But anyway, there was only one position there.
Let me check the settings of a sub-account more. So, nothing you can see on bot’s site?
On bot side I can see only that the liquidation message was received from the exchange.
By the default, I am seeing, the sub-accounts have their Futures settings set to Isolated. Can the bot forced the change to cross, and also force the leverage settings? We’re speaking now specifically about KuCoin.
Do you have other bots on the same symbol, or just only one? In kucoin it could be a problem when multiple bots has each own leverage or margin.
Nope. This sub-account is running just one bot one just one coin.
So, in general KuCoin Futures is a bit more exotic, as I can see… maybe we’re missing something. I am re-starting the bot and observing it again.
The bot doesn’t liquidate a deal, the exchange does, the bot is only notifying you about it. Each exchange has it’s own rules, you may need to check with them why it was liquidated if you still had margin but my guess is that the margin needs to be manually added, meaning just because it’s in your account doesn’t mean it will use it. But support can confirm that.
How are you forcing the leverage setting? So here’s what I am observing:
The bot settings, as I’ve shown above is Cross, 12x
When bot opens position, things get messed up:
So, upon the start, the bot does not force its settings. Then I end-up having an “Isolated” budget with some strange leverage, and a liquidation price…
I have another interesting observation, guys. It looks like KuCoin Futures is not allowing to change leverage type on some coins, i.e. some coins can be Cross leverage, but some stay as Isolated, and I do not see an option to change this…
This is expected of Kucoin Futures.
I will check whats with margin type.
So, let’s say in theory I will put Isolated in Ganium, but will give it all my account’s budget. But, as you know, Combo bots open and close continuously. Where can we specify the amount of Isolated budget that would be set at each bot’s restart.
Or, in other words, how does this option in Ganium really works?
You cannot give to Isolated position any budget in advance, it will use only funds locked in the positions. With each buy position will be increased and with each sell will be reduced.
Maks, did you put a fix there? Now I am getting an error when trying a different pair.
I am not sure if your fix code is correct, though, because I specifically put Cross 12x on SUI, on my exchange and that’s also the same thing I have on the Combo bot 679797511154c67fc6c4fde2
No, I didnt change anything. This is direct response from the exchange, not the bot.
Ok, thanks for responding.
KuCoin is driving me crazy. Now when I actually match the leverage, it tells me it does not match. I tried already several pairs. And before, when things were NOT matching, it allowed the bot to run. 
Yes, correct. Some pairs doesn’t support cross mode. We will show notification in the settings after next update.
