Support Board
Date/Time: Mon, 13 Jan 2025 02:06:09 +0000
child order becomes orphaned (rithmic, sc 1522)
View Count: 571
| [2017-03-28 01:03:08] |
| onnb - Posts: 662 |
|
We are seeing following We place an order with OCO. Initially child's ParentIntenalOrderId is set to parent and all is good. After some time we see this in the log Rithmic Trading order update (Restated). Info: Status: modified, trigger pending. Rithmic Trading order update (Restated). Info: Status: open. At this point the column for the ParentInternalOrderId is empty - in other words, the order looks like its orphaned. This causes a mess for us as we need to know that this order is a child order. This looks to be happening on build 1522. We had another system running parralel to this one, taking the exact same trades on build 1490 and the trade was ok - ParentInternalOrderId was kept intact. Are you familiar with any of this? Date Time Of Last Edit: 2017-03-28 01:03:42
|
| [2017-03-28 05:40:59] |
| |
|
Do you know if the particular Rithmic username/account has more than one trade account assigned to it? If so, update to the latest prerelease, 1535, because there was a problem with refreshing of the order list when there is more than one trade account when using Rithmic. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
To post a message in this thread, you need to log in with your Sierra Chart account: