Support Board
Date/Time: Tue, 16 Jun 2026 04:40:00 +0000
Post From: DTC API: Orders stuck in
| [2026-06-15 21:47:41] |
| User808121 - Posts: 1 |
|
Hi Sierra Chart Support, I am encountering an issue with externally submitted DTC orders that do not execute and remain permanently stuck in "Open" status. Environment: • Data Feed: Denali Exchange Data Feed (providing active market data and depth). • Trading Service: Rithmic 01 (Live connection). • Routing Configuration: The Rithmic connection is strictly used for Live Order Routing, NOT for market data. • Trade Simulation Mode: Enabled (Trade >> Trade Simulation Mode On) as a safety shield. • DTC Server: Enabled on 127.0.0.1:11099 (Package 11) • DTC Client: External Python application • Target Account: Sim1 • Target Symbol: ESU26-CME[M] (September 2026 contract) The Issue: My Python application successfully logs into the local DTC server and submits a Buy Market Order using SUBMIT_NEW_ORDER_INTENTS (Message Type 208). Based on the platform logs, the DTC order is successfully received and processed by the local server, but it gets blocked right before the execution stage. Sierra Chart's Trade Activity Log confirms packet receipt with the line: "Sending Position to DTC clients. Symbol: [Sim]ESU26-CME[M]. Trade Account: Sim1". However: • The order status remains indefinitely stuck in "Open" status instead of transitioning to "Filled". • No fill is generated and no position is created. • The Trade DOM remains completely flat despite active market data and moving prices for ESU26-CME[M]. • Right after the order freezes, the Message Log flags: "Flagging to reload Trades list in charts". Additional Observation: If I instead submit the order targeting my live Rithmic routing account identifier while the global "Trade Simulation Mode On" shield remains enabled, the Message Log throws the following explicit routing error: "Non-simulated Trade Account [My_Live_Account_Number] cannot be used with Trade Simulation Mode | Symbol: [Sim]ESU26-CME[M]" This confirms that the DTC packets are reaching Sierra Chart correctly, but there appears to be an internal routing or validation conflict when handling external simulation orders while the platform is authenticated on a live Rithmic server used purely for order routing. Questions: 1. Is "Sim1" the correct account identifier string to send via DTC orders intended for the internal Sierra Chart Trade Simulator? 2. Are additional DTC Server settings or checkboxes required to allow external market orders to immediately execute (Fill) against the internal simulator? 3. Can the internal simulator be used through DTC while the platform is connected to a live Rithmic service strictly for live routing? 4. Are there specific symbol or account naming conventions required for simulated DTC orders when a live routing bridge is active? 5. Does the DTC server require a simulated symbol format (for example [Sim]ESU26-CME[M]) instead of ESU26-CME[M] when Trade Simulation Mode is enabled? I can provide DTC packet captures, Message Log entries, and Trade Service Log output if needed. Thank you for your assistance. Best regards, Caleb |
Private File |