Support Board
Date/Time: Fri, 25 Sep 2026 19:30:54 +0000
Post From: custom DTC trading service — new order not correlating with local order record
| [2026-08-11 04:45:02] |
| User144502 - Posts: 9 |
|
Thank you for the pointer about order IDs needing to be constant and plain ASCII -- that sent me down the right path. I added byte-level logging on every ORDER_UPDATE my DTC server sends and confirmed the order IDs were constant, plain ASCII, and byte-identical to what Sierra Chart sent in SUBMIT_NEW_SINGLE_ORDER every time. The duplicate was still happening, so I kept digging, and wanted to share what I found in case it's useful to you or the next person who hits this. For a pattern-matched Symbol Settings entry, Sierra Chart's SUBMIT_NEW_SINGLE_ORDER arrives with Symbol="" and the resolved ticker in Exchange (e.g. Symbol="", Exchange="CSCO"). My server had been echoing ORDER_UPDATE back with the normalized shape instead (Symbol="CSCO", Exchange="") -- same ticker, different field. Once I changed it to echo Symbol/Exchange back in the exact shape Sierra Chart originally sent them, the duplicate stopped happening -- confirmed across two separate live orders. Before that fix, the pattern was: a second Trade Orders Window row would appear (a new Internal Order ID, LastOrderActionSource showing my server's name) with the real ServerOrderID and status, while the original locally-created "Order Sent" row (matching ClientOrderID, no ServerOrderID) stayed stuck and quietly disappeared roughly 60-90 seconds later. If you happen to know whether Symbol/Exchange shape is intentionally part of order correlation, I'd love to know -- otherwise no need to chase it further on your end, just figured this was worth passing along since it took a while to isolate. Thanks for your help on this! Date Time Of Last Edit: 2026-08-11 04:45:39
|