Since yesterday night, cannot stop bots properly.
Some cannot restart or start.
Been tryin to stop existing bots whole morning.
They are closing deals on “TP timeout” but are not entering any new deals
Also not showing existing Active deal correct number.
Some examples of Affected bots:
682d62079b31542d37b5ee48 - Active deal count shows zero, but there are active deals. Not entering new deals. Aggresive. Similar settings a below. Cannot stop.
682cf7339b31542d37abebb9 - started entering deals (10min ago), but was not since 6-8 hours ago. Very similar settings as above. Cannot stop.
6829a8a54afd7ba560ede8e6 - similar to above. Cannot stop
682cfd429b31542d37ac54ed - aggresive bot, stopped entering since morning, but plausinbe that conditions don’t match. Will backtest to double-check. Cannot stop too
My friend is using Gainium too, and is having similar issues (we have similar bot settings)
P.s… very slow interface today (tried on multiple PCs and VPS) - took me ages to get bot IDs
We’ve received your report regarding the slow and strange performance, including issues with stopping, starting, and restarting bots, as well as incorrect active deal counts and “TP timeout” closures. Thank you for including the bot URLs. We are looking into these issues and will provide an update shortly. We appreciate you bringing this to our attention.
The issue related to indicator actions has been resolved. All processes have been completed, and the logic has been updated. You can now operate your bots.
One has stopped, but took ages. Also canceled all the deals.
This one however, still running: 682cfd429b31542d37ac54ed
Despite canceling the last deal.
These are heavy bots. Along with indicators, they a futures and have many symbols to work with. On each start we are checking position config for each symbol. Start could take few minutes to be finished, depending on exchange load. Bybit exchange limits are count against user not the ip, so it also depends how much simultaneous operations of your bybit account (not only Gainium).
Somewhere between start/stop/reload bot stuck. I made few updates to prevent. Also I updated when bot status changed. Bot will wait to fully connect or disconnect all indicators, also finish side jobs before changing status. In your case, after you will see the notification about bot operation is scheduled, I suggest to wait until bot actual status will be changed and then perform new operation.