Support Board
Date/Time: Wed, 19 Aug 2026 02:25:56 +0000
Post From: AMP Global - CQG or Teton for EA ACSIL System
| [2026-07-02 16:10:01] |
| John - SC Support - Posts: 47538 |
|
With Teton Order Routing, is a stop order — including an attached stop submitted and modified by an ACSIL study — held server‑side (at Teton/the exchange), so it remains working and will execute if my Sierra Chart client disconnects, loses data, or the machine goes down?
A standard Stop (or Stop-Limit) is held on the exchange. This will be true with any order routing service. Special stop orders (such as Trailing Stop) will be on our servers and processed on our servers for a Teton connection. For other order routing services, this would not be case, so your local Sierra Chart would need to be running in order to update the order with each change. But, you state that you are modifying the order using your custom study, therefore, each update occurs only on your local Sierra Chart, where your study is running, and then the updated Stop order is sent to the exchange. As such, the order routing service does not come into play at all. When my study modifies that stop each bar, does each accepted modification leave a working server‑side stop at the latest price — i.e., if I disconnect immediately after a modify, does the most recently accepted stop level stay live and execute at Teton?
As noted above, with any order routing service, the last modification will be at the exchange. Does Teton support server‑side OCO/bracket (stop + target) orders that survive a disconnect, and if so what must I enable?
Teton supports server side OCO/Brackets. There is nothing special you need to do, this is always the way it works. Does Teton offer a native server‑side trailing stop order type (so trailing continues while my client is offline), or only static stops my client must keep updating?
There are built-in trailing stop orders within Sierra Chart. As noted above, if using one of these with Teton, then the trailing will continue to process even if your local Sierra Chart is not connected. Refer to the following for a "Trailing Stop", but review the other order types that are available: Order Types: Trailing Stop What order settings are required for the stop to persist through a disconnect — GTC vs Day, any "server side" flag, specific order types, or Teton/CME configuration?
There is nothing that needs to be done with this for Teton. The "Time in Force" has nothing to do with this. Choose the "Time in Force" you want based on your needs. Although the CME Group only accepts "Day" and "Good tile Cancelled". Does Teton or Sierra provide any server‑side risk management / auto‑liquidation that would flatten an open position if my client stays disconnected?
No. For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |