Support Board
Date/Time: Tue, 25 Aug 2026 19:54:21 +0000
Teton server-side bracket behavior when protective NQ StopPx is already crossed
View Count: 43
| [2026-08-24 09:07:25] |
| User935906 - Posts: 2 |
|
Hello Sierra Chart Engineering, I am evaluating a move from CQG to Sierra Chart Teton through AMP Futures because I trade a latency-sensitive NQ scalping strategy. This is not high-frequency trading: maximum two entry trades per day, but potentially 10-25 contracts per order. My primary concern is preventing a filled parent position from remaining without a valid protective stop at CME. My understanding from your documentation is that Teton manages bracket orders server-side and submits the attached protective stop to CME in under one millisecond after the parent fills. Please consider this exact example: - A Long NQ parent fills at 30,000.00. - The intended protective Sell Stop price is 29,993.00. - Before Teton submits the protective child to CME, the market has already traded below 29,993.00. Scenario A: The current market is 29,990.00, below the original StopPx but still inside the original 15-point NQ CME protection range. Scenario B: The current market is 29,976.00, below both the original StopPx and the complete original protection range, whose lower boundary would be 29,978.00. Please answer each question directly: 1. Are the complete attached child-order instructions stored on Teton’s servers before the parent fills, or is any part of their activation dependent on the Sierra Chart desktop client? 2. What exact CME iLink order does Teton submit when the original protective StopPx has already been crossed before the child reaches CME? Is it: - an unchanged OrdType 3 Stop Order with Protection; - an OrdType 1 Market Order with Protection; - a Stop Order with an adjusted StopPx; - or another order type? 3. Could CME reject the protective Sell Stop under reject code 2060 because its StopPx is no longer below the last traded price? Please also confirm the corresponding behavior for a protective Buy Stop and reject code 2061. 4. If CME rejects the protective child, does Teton automatically: - submit a valid replacement protective order; - submit a Market Order with Protection; - immediately flatten the position; - or only report the rejection while leaving the position open? 5. Does Teton’s handling differ between Scenario A and Scenario B? In Scenario B, can any quantity remain unfilled at the original CME protection-price boundary while the market continues moving away? 6. Has this exact stale-StopPx behavior been verified through an actual CME acknowledgment in production or CME certification, rather than only through an internal simulation? 7. For a partial parent fill, are protective children activated immediately for the currently filled quantity before the remaining parent quantity fills? Are the protective quantities then automatically increased as additional parent fills occur, so the currently filled position is protected at all times? Last-resort account protection: 8. Does Teton support a server-side Daily Net Loss Limit for an AMP Futures account that remains active when Sierra Chart is closed, the VPS fails, or the client loses Internet connectivity? Please confirm whether it can be configured to: - continuously include both realized daily P/L and unrealized open-position P/L; - cancel every working order when the limit is reached; - immediately flatten every open position; - prevent new or position-increasing orders for the remainder of the trading day; - and operate independently of the Sierra Chart desktop client. 9. If a protective bracket child is rejected and the position remains open, will the server-side Daily Net Loss Limit continue monitoring that unprotected position and automatically liquidate it when the configured threshold is crossed? 10. How frequently is the Daily Net Loss Limit evaluated? What order type is used for liquidation, and can the actual final loss exceed the configured threshold because of latency, liquidity, slippage, CME protection limits, or an exchange halt? 11. Must AMP configure and lock this Daily Net Loss Limit, or can the trader configure it directly? How can I verify before trading that the Daily Net Loss Limit and “Flatten Positions at Daily Loss Limit” are enabled on the Teton server? The critical question is whether Teton provides a valid exchange-accepted fallback when the intended protective Stop price has already been passed before the child reaches CME, with the Daily Net Loss Limit acting as an independent final safety layer. Thank you, Jeremy |
| [2026-08-25 17:22:58] |
| Sierra_Chart Engineering - Posts: 24659 |
|
Sierra Chart has a feature for this: My primary concern is preventing a filled parent position from remaining without a valid protective stop at CME.
Refer to:Global Trade Settings Windows: Auto-Send Market Order On Rejected Stop Attached Order (Global Settings >> General Trade Settings >> General) Yes: My understanding from your documentation is that Teton manages bracket orders server-side and submits the attached protective stop to CME in under one millisecond after the parent fills. In the two scenarios you give above A and B, the exchange would reject the stop order. This is 100% definite. ------ 1. Are the complete attached child-order instructions stored on Teton’s servers before the parent fills, or is any part of their activation dependent on the Sierra Chart desktop client? 2. What exact CME iLink order does Teton submit when the original protective StopPx has already been crossed before the child reaches CME? Is it: - an unchanged OrdType 3 Stop Order with Protection; - an OrdType 1 Market Order with Protection; - a Stop Order with an adjusted StopPx; - or another order type? 3. Could CME reject the protective Sell Stop under reject code 2060 because its StopPx is no longer below the last traded price? Yes of course. And you should know that. It is going to be immediately rejected.4. If CME rejects the protective child, does Teton automatically: - or only report the rejection while leaving the position open? 5. Does Teton’s handling differ between Scenario A and Scenario B? no difference.In Scenario B, can any quantity remain unfilled at the original CME protection-price boundary while the market continues moving away? Yes.6. Has this exact stale-StopPx behavior been verified through an actual CME acknowledgment in production or CME certification, rather than only through an internal simulation? This question makes no sense at all. This is a common scenario encountered in production all day long every day. It is so common, for users to submit stop orders that get rejected. It has been tested time and time again. It is nothing more than a rejection of an order. There is no problem handling that. We do not even understand why something is being questioned that is so basic. And the use of the term "stale" makes no sense. There is no such terminology that is even applicable here.7. For a partial parent fill, are protective children activated immediately for the currently filled quantity before the remaining parent quantity fills? Yes of course. Are the protective quantities then automatically increased as additional parent fills occur, so the currently filled position is protected at all times? Yes of course. This is all very basic.8. Does Teton support a server-side Daily Net Loss Limit for an AMP Futures account that remains active when Sierra Chart is closed, the VPS fails, or the client loses Internet connectivity? Yes.Please confirm whether it can be configured to: Yes. Open position PL is absolutely included otherwise the functionality would make no sense.- continuously include both realized daily P/L and unrealized open-position P/L; - cancel every working order when the limit is reached; Yes of course.- immediately flatten every open position; Yes of course.- prevent new or position-increasing orders for the remainder of the trading day; Yes of course.- and operate independently of the Sierra Chart desktop client. Yes of course.9. If a protective bracket child is rejected and the position remains open, will the server-side Daily Net Loss Limit continue monitoring that unprotected position and automatically liquidate it when the configured threshold is crossed? Yes of course.10. How frequently is the Daily Net Loss Limit evaluated? At least twice a second.What order type is used for liquidation, and can the actual final loss exceed the configured threshold because of latency, liquidity, slippage, CME protection limits, or an exchange halt? Market orders. Yes the final loss could exceed the set limit. You should know that. There can be no doubt about that.11. Must AMP configure and lock this Daily Net Loss Limit, or can the trader configure it directly? Your broker needs to do this. How can I verify before trading that the Daily Net Loss Limit and “Flatten Positions at Daily Loss Limit” are enabled on the Teton server?
Refer to: Sierra Chart Teton Futures Order Routing: Understanding the Daily Net Loss Limit Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2026-08-25 17:30:41
|
| [2026-08-25 17:35:50] |
| Sierra_Chart Engineering - Posts: 24659 |
|
Our experience with CQG, is that it is very substandard compared to Teton order routing in so many ways including handling of bracket orders. We explain a lot of this here: Sierra Chart Teton Futures Order Routing: Introduction Considering all of the questions that you are asking, this only confirms that CQG is exceptionally substandard compared to Teton order routing. We do not even know why anyone would be using CQG at all for CME trading. You are throwing money away with a substandard service. With Sierra Chart Teton order routing you pay nothing. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2026-08-25 17:37:44
|
| [2026-08-25 18:01:08] |
| User935906 - Posts: 2 |
|
Hello Sierra Chart Engineering, Thank you for the detailed response. I understand that rejection of an invalid Stop price is standard exchange behavior. My remaining question is not about the rejection itself, but about the execution location and failure-domain independence of Sierra Chart’s replacement mechanism. Please distinguish between: 1. Teton’s server-side management of the original bracket; and 2. the separately configured “Auto-Send Market Order On Rejected Stop Attached Order” function. Please consider this exact sequence: - “Use Server Side Bracket Orders” is enabled. - “Auto-Send Market Order On Rejected Stop Attached Order” is enabled. - A parent order with attached Stop and Target is accepted by Teton. - Sierra Chart is then completely closed, or the computer and Internet connection fail. - The parent subsequently fills. - Teton submits the attached Stop to CME. - CME rejects that Stop because its Stop price has already been crossed. Without any running or connected Sierra Chart desktop client: 1. Does the Teton server itself receive and process the CME rejection and automatically submit the replacement Market order? 2. Is the “Auto-Send Market Order On Rejected Stop Attached Order” instruction stored on the Teton server as part of the server-side bracket configuration before the parent fills? 3. Will the replacement Market order cover the complete currently unprotected filled quantity, including any partial parent fills? 4. Or does this functionality require the Sierra Chart desktop application to remain running and connected in order to receive the rejection and submit the replacement Market order? The standard Stop rejection behavior is already fully understood. The only remaining issue is whether the replacement Market order is fully server-side and client-independent when using Teton server-side brackets. This distinction is important because the purpose of server-side risk protection is specifically to remain functional during a client, computer, VPS, or Internet failure. Thank you, Jeremy |
To post a message in this thread, you need to log in with your Sierra Chart account: