Support Board

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.

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?

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?

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?

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?