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)
About a week or two ago, I was stopped into a long trade, and price immediately ticked against me 6 or 7 ticks, and my stop was set to be 5 ticks. By the time the stop order was placed, it was above the market, which is a no-no for sell stops, and I got an error and was left with an unprotected open position.
So, the moral of the story is monitor what's going on when a trade is entered. Race conditions exist and there is no guarantee of orders getting placed correctly.
Exactly! This has happened to me many many times because OCO's reside on your workstation. You have to keep flashing back to your logs/open positions chart! Don't trust the GUI interface.
I am still trying to understand where things are executed as it seems a little unclear. I am using CQG as my data provider and I expected my profit target to hit on Thursday morning. I had a protective stop in the market too. I switched off the computer and went for lunch, came back and noticed price hit my target but no execution had occurred, and price had since retraced and passed my SL too. I am using Ninja through AMP/CQG. I requested some support on this and never got any response. Reading this message though, it sounds as if OCO's run client-side? Thats just stupid. I thought this was a server side piece of functionality.
From my experience with Ninjatrader7 OCO, and Stops. Targets are Client side residing on your machine, so if you turn off your computer , or Lose connection you have lost your Order management.
I like using NT, but i have considered other platforms for Server side held Orders, as Rithmic RTader, and others like
CTS T4 server-side OCO integration with Sierra Chart offer.
OCO orders for NinjaTrader through CQG are server side. You mention that you requested support for this but never received a response...You did not clarify if this was requested through AMP or NinjaTrader. If the latter, please post your ticket # and I will promptly follow up with my team on this.
@ NinjaTrader ...based on your response pointing towards Data Provider CQG, and that OCO orders reside on Server
side.
Is this issue with Orders like OCO, Stops, and Targets all have to do with what Data Provider one uses to power the Platform ?
In other words is there a Data Provider i can use that allows me to place those Orders through Ninjatrader,and they will be at the Exchange, and will not have to worry about my machine, or internet connection going down.
Also will Ninjatrader 8 be any different with Order management based on where Orders are held ?
I tried to find earlier posts in futures.io (formerly BMT) that have covered these types of questions but unfortunately could not find it.
- Orders submitted through NinjaTrader reside at the exchange...this has always been the case
- OCO orders are NOT native exchange order types thus they must be handled by our brokerage technology providers and if not, then NinjaTrader handles it locally