SL triggering to early

Bug Reports
1

Bug info: I’m using a manual bot using a default template (0.25 SL, 0.5 and 0.75 TP)

Today I noticed my orders would close almost immediately within seconds. The price movement / price action was only 0.01% at the moment, see the attached screenshot. The top 3 are the failed orders which closed in seconds, the last one is from a few weeks ago which was correct.

Maybe due to the changes in Bybit fees? Seems after starting the bot it already thinks I’m in loss due to the fees.

My expectation would be that the % SL reflects only the the price movement and doesn’t include the paid fees. (Which is also ‘loss’ but makes it difficult to calculate SL)

IMG_4648
IMG_46481179×1336 134 KB

2

Need a bot ID to investigate.

3

Ofcourse: Gainium app

4

Its bot a bug. Its a fee update. Already mentioned to by other users.

From our side I can confirm, that you have 0.15% maker and 0.25% taker, which is lead to almost immediately closing of the deal with your settings.

5

Wouldn’t it be better if the stop loss would work independently of the fees at the configured deviation?

1 Like
6

Ok, and then users will ask, why I set to 0.25% and deal was closed at 0.55%? Fee is taking into account when calculating exit price.

7

But wouldn’t that be as for the take profit, which is increased to recoup the fees for open and close orders including the configured take profit? Or what happens if we configure a take profit, that only matches the resulting fees?

8

Fee added to deviation. If you set TP to be 1%, it will be set at 1.15%. If SL deviation set to -0.25%, SL target price will be calculated based on 0% (-0.25% + 0.25%).

9

So if the fees are 0.2% in total and we configure a take profit of 1%, the deal would close would close at 1.2%. We would have gained 1%.

If we configure stop loss with -1%, the deal would close at -0.8%. We would have lost -1%.

So that setup makes sure that if we start with the same price the gain of 1% take profit and the loss of 1% stop loss adds up to 0.