Maybe turn on “tick by tick” and then see that the system doesn’t work that way?

Here are some clues about differences https://www.prorealcode.com/topic/backtesting-and-demo-account-algo-doesnt-match-live-algo/#post-175691.

Try changing line 33 with a greater value, such as 10 or 20.

A better solution would be to use a custom made trailing stop. here is the easiest to use https://www.prorealcode.com/blog/trading/complete-trailing-stop-code-function/. Just comment out line 33, then append lines 17 through 56 from the code snippet. Its settings are 20 and 5, you may also try 20 and 10 or 20 and 20, etc…

In this spreadsheet https://docs.google.com/spreadsheets/d/1rgboqj7sVwsP9ZRhOduOefye48QMWC07jWVXCl-KJPU/edit#gid=0, maintained by GraHal, you will find so many links to useful code snippets.

Hi there Martin,

// Definitie van code parameters
DEFPARAM CumulateOrders = False // Opstapelen posities gedeactiveerd
// Het systeem zal alle lopende orders annuleren en alle posities sluiten om 0:00. Er zijn geen nieuwe toegestaan totdat na de "FLATBEFORE" tijd.
DEFPARAM FLATBEFORE = 000000
// Annuleer alle lopende orders en sluit alle posities op de "FLATAFTER" tijd
DEFPARAM FLATAFTER = 171500

// Voorkomt dat het systeem nieuwe instaporders plaatst of de positie vergroot voor een specifieke tijd.
noEntryBeforeTime = 000000
timeEnterBefore = time >= noEntryBeforeTime

// Voorkomt dat het systeem nieuwe instaporders plaatst of de positie vergroot na een specifieke tijd.
noEntryAfterTime = 163000
timeEnterAfter = time < noEntryAfterTime

// Condities om long posities te openen
indicator1 = CALL "MAGICAL TREND"[13, 1.5](close)
c1 = (close > indicator1)

IF not onmarket and c1 AND timeEnterBefore AND timeEnterAfter THEN   // !
  BUY 1 CONTRACT AT MARKET
ENDIF

// Condities om short posities te openen
indicator2 = CALL "MAGICAL TREND"[13, 1.5](close)
c2 = (close < indicator2)

IF not c1 and not OnMarket and c2 AND timeEnterBefore AND timeEnterAfter THEN   // !
  SELLSHORT 1 CONTRACT AT MARKET
ENDIF

//************************************************************************
//trailing stop function
trailingstart = 20 //trailing will start @trailinstart points profit
trailingstep = 10 //trailing step to move the "stoploss"
 
//reset the stoploss value
IF NOT ONMARKET THEN
  newSL=0
ENDIF
 
//manage long positions
IF LONGONMARKET THEN
  //first move (breakeven)
  IF newSL=0 AND close-tradeprice(1)>=trailingstart*pipsize THEN
    newSL = tradeprice(1)+trailingstep*pipsize
  ENDIF
  //next moves
  IF newSL>0 AND close-newSL>=trailingstep*pipsize THEN
    newSL = newSL+trailingstep*pipsize
  ENDIF
ENDIF
 
//manage short positions
IF SHORTONMARKET THEN
  //first move (breakeven)
  IF newSL=0 AND tradeprice(1)-close>=trailingstart*pipsize THEN
    newSL = tradeprice(1)-trailingstep*pipsize
  ENDIF
  //next moves
  IF newSL>0 AND newSL-close>=trailingstep*pipsize THEN
    newSL = newSL-trailingstep*pipsize
  ENDIF
ENDIF
 
//stop order to exit the positions
IF newSL>0 THEN
  SELL AT newSL STOP
  EXITSHORT AT newSL STOP
ENDIF
//************************************************************************

I applied two small changes at the // ! lines. Now it works technically OK. Whether functionally is up to you.
Notice that in Backtest it was already wrong; please observe the immediate exits in your original code.

I hope this helps you !
Peter

Apologies if already been discussed, but do you have the exact same spread set in the backtesting engine as in Live (varies over 24 hours)?

Apart from a few points + or – in profit, differing spreads (backtest to Live) could even affect trades being placed or not (depending on code).