Support Board
Date/Time: Tue, 25 Aug 2026 19:51:47 +0000
Post From: Teton server-side bracket behavior when protective NQ StopPx is already crossed
| [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 |