Trailing stop not working as expected, then suddenly starts to work
- This topic has 7 replies, 4 voices, and was last updated 5 years ago by
.
-
then it suddenly jumped.
Trailing Stops (TS) can do this depending on the type / setting of the TS. You don’t say what type of TS you are using or better still provide the code so we all have to guess! 🙂
TS can have a threshold value and then a step value … for example a 30 point threshold before the TS moves the 5 points step.
Hope that makes sense?
1 user thanked author for this post.
I see many rejected orders in the list, what kind of trailing stop do you use? a SET STOP PTRAILING?
1 user thanked author for this post.
What happen if the Close[1] value is very tight? You should not use SET STOP PTRAILING with this kind of calculation. Be aware that SET STOP PTRAILING performs not the same way in backtests than on real/demo accounts because of the minimal stop distance defined by the broker for the step value (it usually makes the backtests much better than in real life).
Anyway, the main problem here is that the value you set is not respecting this behavior and therefore the trailing stoploss is rejected.
For example, if the DAX minimal stop distance is 5 points, you could modify the code like this:
1SET STOP pTRAILING max(5,close[1]/200)For trailing stop functionnalities, you should use coded versions that exist around in the forums.
1 user thanked author for this post.
Find exclusive trading pro-tools on 
