time in log is way off from time of my machine

[SteveReiza]

my strategy has a bool for timefortrade and its executing out of the hours of the bool and i'm not sure why. but, here is a snapshot of the log. and, it has a timestamp that is way earlier than me. is there a place where you set time for the instrument other than in the data series? i changed the 'trading hours' for the instrument to be pacific time. but, i'm thinking there is somewhere else.

[NinjaTrader_Jesse]

Hello SteveReiza,

The warning that you pictured is letting you know that during the historical backtest the order that was submitted had prices that were outside the range of the bar so it was ignored. The timestamp is the historical timestamp of the bar.

[SteveReiza]

thanks for the reply. for some reason the strategy gets un-enabled. and, i check the log and that's there. is there any way to get that to stop affecting my strategy being enabled.

[NinjaTrader_Jesse]

Hello SteveReiza,

That warning is not something which can disable a strategy, that is just letting you know 1 order was ignored. The strategy is likely being disabled if you have an error in your code, you would need to review the log and find where the strategy was disabled to see if there is an error or rejection listed.

[SteveReiza]

thanks for the reply. alright i'll check into doing prints and trace.

question. why is something that happened hours before affecting an order in the present? an order being ignored isn't good.

[NinjaTrader_Jesse]

Hello SteveReiza,

That depends on what you coded. If your logic was expecting an order but it was ignored for the given reason there could be no further trades. This comes down to how your strategy works and if it can accommodate that. Using prints is the best way to identify what happened in your specific script so you can see how it logically worked after the order was ignored.

[SteveReiza]

thanks for the reply. alright, i'll check out using prints.