Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
why do I get this from time to time when replay testing . . .
It's a common problem with NinjaTrader in a fast moving market, NT throws this error instead of gracefully handling it. You can disable the handling of orders with NT and do it all yourself, if you are an extremely advanced programmer.
Mike, excuse my ignorance, but, when this happens, does NT go ahead & exists all my positions (if any) AND goes ahead and stops executing the strategy ?
It's been a long time but if memory serves, it just halts the strategy. I can't remember if it closes open positions or not, but I am thinking not. You would be better served asking NT support or doing your own homework to be 100% sure on that one.
In any market, fast or not, NinjaTrader does not control when this error occurs. This error is an invalid order price and is triggered by the exchange. Our simulator replicates where possible general exchange order handkling rules which is why this invalid price error is triggered in the market replay engine.
When an order is rejected in a strategy, NinjaTrader gracefully handles this with default action of halting the strategy and putting it into a state so that the strategy can't do any damage and provides notification to the developer via email as an option. We also provide the ability to override this default behaviour so that the system developer can account for exceptions and determine how best to deal with it.