I’m running a NinjaScript 8 strategy (Managed Approach) on a Tradovate-connected account (Apex prop firm simulated/demo environment, not live funded) trading PL futures. The strategy uses SetStopLoss(signalName, CalculationMode.Price, candidateStop, false) to move the stop to breakeven and then trail it, called dynamically from OnBarUpdate() while in a position. On 11 Aug 2026, a short position entered at 13:24:01 (entry price 1766.7) had its stop moved to breakeven at 13:35:00, then trailed further three more times, with the last logged move at 14:17:00 placing the intended stop around 1758.5 (a ~$150 trail distance behind the best price reached). My strategy’s own event log (with TraceOrders = true enabled) shows a BREAKEVEN_STOP_ARMED event and three subsequent trail-move events, all without any error reported. However, the trade’s actual exit — confirmed via the Orders grid — shows only a single stop-loss order for this position’s OCO group, with a stop price of 1769.5 (order ID 614057190183, OCO 614057190177_1), filled at 14:39:31. That 1769.5 level is the trade’s original nominal stop distance (30 ticks from entry), not the trailed level the strategy log claims was set. There is no second stop-loss order or price-amendment record in the order history for this OCO group - the live order appears to have never actually moved, despite the strategy’s internal state and log believing it had been successfully modified three times. I can provide the full TraceOrders output, the strategy’s filter log, and the Orders-grid export for this trade if that helps investigate. Is this a known interaction between SetStopLoss() price amendments and the Tradovate connection, and if so, is there a recommended workaround (e.g., cancel-and-resubmit instead of a price-only amend)?
This behavior is only in live market or in your simulation account also?