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 15:46:42] |
| User186850 - Posts: 17 |
|
Thanks John. I am setting up a trading robot in Sierra using ACSIL. I am concerned about data loss associated with a naked position if internet or Sierra disconnects and having the wrong service package setup. I'll be more specific. Subject: Does a Teton attached stop remain working server‑side if my Sierra Chart client disconnects? I run an automated ACSIL study (current Sierra Chart version) that scales into a futures position and protects it with a single attached stop order, which the study reprices with ModifyOrder on each bar to trail it. I currently route AMP + CQG Web API with Denali data, and I'm moving to Teton Order Routing specifically because I need the protective stop to survive a data/connection loss. My concern is risk of ruin if my Sierra Chart instance loses its data feed or internet, or the VPS/PC shuts down, while a position is open. Please confirm: 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? 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? Does Teton support server‑side OCO/bracket (stop + target) orders that survive a disconnect, and if so what must I enable? 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? 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? Does Teton or Sierra provide any server‑side risk management / auto‑liquidation that would flatten an open position if my client stays disconnected? I want the exact configuration that guarantees a resting protective stop executes even with my client fully offline. Thank you. |