Bug info:
2.nd time now, buy order triggered on bybit but limit sell and buy orders did not arrive at exchange.
Need to restart manually to send limit orders again.
Happend around 17:45 (gmt+1)
Bot URL → Gainium app
[Optional] Steps to reproduce →
Expected result →
Same thing now at 09:00.
This is ending in Liquidation if this is not working correctly.
I am loosing trust in Gainium, too much bugs and loosing money.
That’s not fun at all!!!
I’m checking your bot and don’t understand your problem. Buy and sell orders placed after deal started (order id that starts with CMB-BO is deal start order). There are no delays whatsoever.
Can you explain what do you mean by order did not arrive at exchange? Is not visible in the app or in the exchange? I can see in the logs that orders are arrived and accepted by the exchange.
The problem was here before restarting the bot manually.
The orders have been created in gainium but they never arrived in bybit‘s order list.
It just opened a position with 0 open orders. After restarting the bot manually all limit orders sent again and finally settled in bybit
So, these lines “Order created” mean that order was created in Gainium, sent to Bybit and accepted by Bybit. I can see it in logs, the exchange responsed with order id and status NEW.
Where did you check that order not arrived in bybit? Is it bybit app or web? Did you try to refresh bybit page?
I checked it mobile at the bybit app.
Did not refresh anything because normally it is refreshing automatically.
Try to make a screenshot next time when with the exact time when happened and also checking on web.
I can confirm that from our side all was done normally. Next time please try to refresh the app first. And also check order lines in Gainium chart.
Today everything was fine. Orders arrived as it should be.
Watching closely now and opening a new request when it happens again.
One more question,
As i understand it correctly, when i have a stop loss setting in Gainium, it is monitoring the 1min (or in my bot 3min?) candle, correct?
Is it also possible to make the stop loss based on the body of the candle and not to the wick?
I want to avoid a stop loss, if the price moving out of it immediately.
Happened here:
Thx for clarifying
The price on close should tell the bot when to close a deal. If the price is above the stop loss then, the deal should stay open.
We check SL condition based on real time price update, not candles. In this case there was a delay due to system update.
Okay, but is there a idea how I can prevent those liquidity grabs in the bot?
I don’t want a higher stop loss setting because the lower profit in backtesting. But it happened the third time the liquidity grab is hitting the bots SL on max. DCA and moved up after.
I don’t think it’s possible. Like maksym said the bot doesn’t receive candles, it receives real time prices that can change in mili seconds. Candles are formed after the fact. The bot cannot possibly know what the body of the candle is before the candle has formed.
What you propose is a dump protection, where there could be a delay before triggering the stop loss. If after the delay the price has recovered then it won’t execute it. You can make a feature request for that.
Is there a stop loss timeout that delays the stop loss after it was triggered? Of course, this could also result in losses.
