I'm backtesting a strategy that runs on daily data and places entry orders
via OnExecution when an exit takes place and via OnOrderUpdate when an order cancelation takes place. It works fine in general but there are a few bars where no entry orders are placed, although there is a prior exit or cancelation.
Not sure what's the reason, is it eventually a known issue that some
events are "missed" by NT or might that be a multithread-issue?
It seems like that
if (exitOrder != null && exitOrder == execution.Order)
{}
isn't reached in those few cases although an exit takes place.
According issue for OnOrderUpdate() and order cancelation.
Thanks in advance for advice,
Stephan

Comment