Short bot error (not enough base for DCA order)->Price dipped until TP price but got stuck->manual close failed->when it finally closed, bot fired unwanted orders

Bug info:
It’s a simple short ASAP bot
Here is the time line :

  1. Bot was running, price pumped, not enough base for DCA sell → Error
  2. Before I had the chance to buy more base to feed required DCA, price dipped and the TP order got filled in the exchange a few hours before.
  3. However deal was still open in bot well past the TP price (and the bot was still in error state).
  4. Tried to close the deal / stop / restart / change TP to wake up the bot from the app,all failed (or delayed?)
  5. When if it finally closed, it fired multiple orders (instead of just one Sell market order to start a new cycle).
  • Bot URL → Gainium app
  • Deal URL → 6785248fa594d51788157a85

screenshot attached

  • Expected result →
  1. Eventhough bot was in error state, but somehow managed to reach TP, then everything should resume normally.

  2. If there is a command sent (Stop/Restart/Cancel) and the app is waiting for a pending response, maybe keep the button greyed out longer to prevent duplicate orders?
    I can see sometimes the button says “Processing” but then its clickable again eventhough the command hasnt been executed yet.
    Anyway the point is to handle “blackouts” like this more gracefully.


Thank you for reporting this issue in detail, and for providing specific timelines, URLs, and screenshots – this information is extremely helpful for diagnosing the problem. We’ve received your report, and our team will investigate the auto-trading behavior and error-handling issues you encountered, such as the stuck deal, delayed manual commands, and the unexpected orders fired by the bot.

We’ll also review your suggestions about improving button responsiveness during command processing and handling error states more gracefully, as these are excellent points. Once we have an update or a resolution, we’ll notify you promptly. Thank you for your patience!

additional info:

Deal history is gone.
I remember this deal had around 7 DCA completed

Buying a volatile currency that is missing for a running deal to DCA, will always spoil the deals statistics. I wrote about that in the article “Tricking” the stats. In the end you again won’t have enough of the currency to close the deal.

the issue here is not about not having enough currency to close the deal, no need to bring up that discussion here.

The bot was in error state because there was not enough base to place another DCA order.
However, even without that additional DCA, the price dipped low enough to reach the TP level, so it should buy it back and close the deal, as simple as that.

and of course I’ve made sure I had enough USDT to buy it back, otherwise how else it managed to buyback even more than initially required.

Have you made sure that this additional USDT is not needed for another deal?

of course.

i checked on available USDT for trade, not just whatever amount I have
no corruption

plus I use KCS to pay for fee… and I have enough KCS of course

and also the USDT reserved for TP (buyback) is locked in limit order, so really no excuse for the deal not to close normally

I clearly stated that “the TP order got filled in the exchange”
Its the bot that didnt act on it, maybe API response delay or something

1 Like

Thank you for sharing the detailed report. We’re currently investigating the issue and working on a solution to address it effectively. Resolving this gracefully is a priority, but it may take some additional time. We appreciate your patience and understanding as we work to improve the bot’s handling of similar scenarios.

Hello,

for comparison, here is an example of another short bot that was in error due to not enough base for DCA, but able to reach TP and proceed with a new deal normally

https://app.gainium.io/bot/6781e35d2889deadb70d999a