Bug info:
As the title says, I found it impossible to open an inverse perpetual bot. I have some balance in SOL that does not allow me to operate from gainium. I can see this balance if I enter my bybit inverse unified account, but I do not see a balance in the exchange section of gainium and obviously the bot doesn’t see it
Bybit
Bybit account connected to gainium
no balance found for sol
Error trying to start the bot in gainium
Fixed, you can try again
Thanks Ares, I’ll try it as soon as I can.
I’ll update you on the case:
Although at first it seemed to work. It detected the balance of the derivatives account in both the exchange and balance section of the bot when I was about to run it, but when I started the bot it gave me a new error:
As it said it was a possible connection error to the exchange, I deleted the reverse derivatives API and returned the API credentials that I have saved from bybit. Then the error that brought me here of zero balance came back 
API keys you added is returning 0 balance and 0 assets in response. Its not the same problem it was before.
The other problem is with UTA 2.0 margin change.
So the problem is the Unified Trading Account? So it is better to stay with the classic Bybit account to be able to separate the balance of the different types of trading? Because what I just saw is not reversible, return from the UTA account to the normal one.
The problem was with UTA 2.0 margin change. That one was fixed. You can try again.
As for balance, at the beginning you added another keys, they return around 600$ balance. New one you added return 0$ and 0 assets in balance.
In itself it was the same keys but I deleted the credentials and put them back in again since I had them saved believing that the previous error ‘related to exchange connection’ was going to be solved but the balance returned to zero again. Now without changing anything and you saying that it was fixed the balance is still zero, should I delete the exchange and put in the same API keys or should I try with a different one?
I would try with a new one. Just make sure the funds are in the right account.
There it worked by changing to a new api key and it read the inverse futures account correctly. Thanks to both of you 
