Bug info:
I’m running a Reverse Futures combo BOT on ByBit and keep getting this error.
Position shows on Gainium but not on the exchange.
- Bot URL → Gainium app
- [Optional] Steps to reproduce →
- Expected result →
Bug info:
I’m running a Reverse Futures combo BOT on ByBit and keep getting this error.
Position shows on Gainium but not on the exchange.
Thank you for reporting this issue, Paulo. We have received your details about the error and will investigate it promptly. Our team will update you shortly once we identify the cause and implement a fix. Let us know if you have any additional details in the meantime.
Does the position exist in the exchange and with enough funds? You can check under Terminal → Positions. If it’s not there then it was liquidated or another bot closed it if you forgot to activate hedge mode.
Nothing on the terminal.
There is no other bots running on this account.
It wasn’t liquidated because the deal closes on profit
The deal still showing on the BOT interface but on the exchange was closed already
I noticed that this happens when a deal is closed.
Unfortunately, I can only upload 1 image.
EDIT: One more info. If I cancel the deal on the bot, another deal is opened normally and the bot continue to works until this deal is close and face the same error again.
If the position is not in the terminal it means is not on the exchange. Not sure how can that happen, I only know two scenarios: 1. It was liquidated (but then the bot should have been notified) or 2. A bot on the opposite direction closed the position because hedge mode wasn’t activated.
You can check on the exchange transaction history exactly when and how that position was closed.
The issue occurs because the bot attempts to place a reduce-only order for a position that doesn’t exist or is already closed on the exchange. While the position might still appear on Gainium, this discrepancy happens due to delayed synchronization with the exchange.
A fix has already been implemented and will be included in the next Gainium update. Once the update is live, this issue should no longer occur. Thanks for your patience!