It must be a bug even though marked "not-bug"

Bug info: This bug report is about an old bug report (from 14/12).
The text says “it’s always spaced *the same from the best price but it is not, so either the bug must be in the code or in the text.

Traling stop loss moves down with a decreasing price

Bug Reports

not-bug

Dec 7

1 / 14

Dec 7

8d

GoodTryerC-Strategy Team

1

18d

Bug info:In teh information about “trailing stop loss” I read:

What is a Trailing Stop Loss

Trailing stop loss is a popular trading technique that enables you to follow the trend. The principle behind it is simple: the trailing stop loss moves in the direction of your take profit, and it’s always spaced the same percentage from the best price.

“it’s always spaced the same from the best price

This is however not the case.
I did set the trailing stop loss to 4% and the initial stop loss value was set to 2.577 but when the price eventually went down to 2.543 the stop loss was lowered to 2.539, where it stayed when the price went up again. The bot also did a sell/and/buy at 19:23:50 at $ 2.627.

When I wasn’t even close to the computer (eating dinner).

  • Bot URL → Gainium app

  • [Optional] Steps to reproduce →

  • Expected result → Since the price went under 2.577 the bot should have sold.

  • Bot URL →

  • [Optional] Steps to reproduce →

  • Expected result →

Response from Maksym:

The lowest price of LQTYUSDT was 2.5747. The trailing level depends on the actual deal start price, which may differ slightly from the estimation displayed during bot creation or editing. This is normal and doesn’t indicate any issue.

I think he compared estimation during creation with the real one when deal was started.

As I wrote; I watched the value of the TSL go down when the price of the coin went down. I have seen it multiple times. According to the text that should not be possible.

Maksym replied:

I already checked it

The lowest price of LQTYUSDT was 2.5747. The trailing level depends on the actual deal start price, which may differ slightly from the estimation displayed during bot creation or editing. This is normal and doesn’t indicate any issue.

I think he compared estimation during creation with the real one when deal was started.


Before the bot launch what you see on the graph repositions with price changes. He also said that the deal you mentioned last time was was not stopped by TSL, but by stop trigger.

Please listen to me. I was watching the screen showing a decreasing value for the TSL. That has nothing to do with what stopped the bot.

Once upon a time Gainium was a well working platform…today, not so much.
Right now I can’t even log in, due to “fail to fetch”
image

After having restarted the computer I could login

I will check again with the dev for the TSL.

I don’t know when a stop loss triggers. Did you check the interbar scenario as well as that on candle close like:

What was the price of the expected stop loss value on candle close respectively interbar. What’s the deviation from the highest candle close/interbar to that candle close/interbar? Is it 4%?

Hello, thank you for your patience. We still can’t reproduce this issue. It would be good if you could do a screen recording so we can see the problem as you see it. Here is what the dev said:

SL order is only shown when bot created or edited. SL order not showing on real deal if deal has trailings sl enabled. SL level calcualted on frontend.

As user said: initial SL value. So this is the value on the screenshot 1, where estimated order are shown, we do not show this value for active deal, if it has trailing sl.

TSL is very simple calculation are working only in one direction when best price changed (increased for long bot and decreased for short bot).

I created dozen of bots with the same settings and I’m not able to reproduce TSL decreasing with decreasing price. Either he did something more which he didnt described or mixed up creating/editing with the real deal.

If we are having problem with TSL, I think we should have more reports on it. The logic os trialing is almost not changed since feature introduction.