Support Board
Date/Time: Tue, 04 Feb 2025 22:44:40 +0000
SC/TT Routing Live Position Order Modification Fail/Issues
View Count: 718
| [2020-02-11 23:46:38] |
| User379468 - Posts: 508 |
|
v2048, live position, initial position 2 contracts with TCW set to two targets, added 2 contracts using same TCW, scale in enabled. 1. After last fill, orders went to 3 contracts at first target, 1 at second target. Why are they bundled this way/how can this be changed to keep equal quantities at each target on scale in? 2. Moving the stop manually failed to execute 3 times. No record in Trade Service Log. Trade Activity Log shows: "Order modification failed | . Internal Order ID: 3464. Service Order ID: 5494. Symbol: ZTH20_FUT_CBOT. Account: ******** | 2020-02-11 11:12:01.239 *" Broker trade desk said they have no reject on their end in TT system, referred to SC support to review for issue/fix. Realized SC/TT Web based order entry system would be incredibly difficult and take forever to cancel orders like these and replace them all manually calculating and typing each one, with the price format of ZT. Had a mini heart attack, then finally cancel all and send new order worked in SC. 3. Trade Service Log is full of the below. Is it possible to hide this/track these queries somewhere else, and keep Trade Service Log clear and usable for actual unexpected Order Fill alerts only like Rejects? TradeActivity files query time: 0.092366 seconds. Entries: 0. Current queries: 2 | 2020-02-11 11:30:34.704 TradeActivity files query time: 0.000707 seconds. Entries: 6. Current queries: 1 | 2020-02-11 11:30:34.704 TradeActivity files query time: 0.007650 seconds. Entries: 0. Current queries: 1 | 2020-02-11 11:30:42.338 TradeActivity files query time: 0.007191 seconds. Entries: 30. Current queries: 2 | 2020-02-11 11:30:42.376 TradeActivity files query time: 0.011657 seconds. Entries: 0. Current queries: 3 | 2020-02-11 11:30:42.421 TradeActivity files query time: 0.007192 seconds. Entries: 3. Current queries: 4 | 2020-02-11 11:30:42.452 TradeActivity files query time: 0.010983 seconds. Entries: 34. Current queries: 5 | 2020-02-11 11:30:42.495 TradeActivity files query time: 0.010291 seconds. Entries: 3. Current queries: 6 | 2020-02-11 11:30:42.538 TradeActivity files query time: 0.007289 seconds. Entries: 3. Current queries: 7 | 2020-02-11 11:30:42.573 TradeActivity files query time: 0.010805 seconds. Entries: 7. Current queries: 8 | 2020-02-11 11:30:42.626 TradeActivity files query time: 0.006802 seconds. Entries: 3. Current queries: 9 | 2020-02-11 11:30:42.652 TradeActivity files query time: 0.011088 seconds. Entries: 3. Current queries: 10 | 2020-02-11 11:30:42.716 TradeActivity files query time: 0.006837 seconds. Entries: 0. Current queries: 11 | 2020-02-11 11:30:42.747 TradeActivity files query time: 0.011711 seconds. Entries: 0. Current queries: 12 | 2020-02-11 11:30:42.812 TradeActivity files query time: 0.007593 seconds. Entries: 3. Current queries: 13 | 2020-02-11 11:30:42.839 TradeActivity files query time: 0.010784 seconds. Entries: 7. Current queries: 14 | 2020-02-11 11:30:42.890 TradeActivity files query time: 0.010580 seconds. Entries: 8. Current queries: 15 | 2020-02-11 11:30:42.943 TradeActivity files query time: 0.010799 seconds. Entries: 8. Current queries: 16 | 2020-02-11 11:30:42.981 TradeActivity files query time: 0.007087 seconds. Entries: 30. Current queries: 1 | 2020-02-11 11:30:43.442 SC Futures Order Routing/Data | Requesting trade accounts from server. | 2020-02-11 11:30:45.052 Date Time Of Last Edit: 2020-02-11 23:46:59
|
| [2020-02-12 03:13:38] |
| |
|
We need you to provide all the information requested here: Trade Activity Log Analysis: Support Assisted Trade Activity Log Analysis And we do charge for this service. And also for the record for your trading account there are no order failures or rejects of any kind for that symbol on 2020-02-11 recorded on the server. None at all. Whatever the issue is, it is not something which is specific to the Sierra Chart order routing service. 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 Date Time Of Last Edit: 2020-02-12 03:17:59
|
| [2020-02-12 23:22:48] |
| User379468 - Posts: 508 |
|
Whether SC routing service or SC software local in charting instance, need to find the issue, cannot be in live positions unable to move stops. "Order modification failed | . Internal Order ID: 3464. Service Order ID: 5494. Symbol: ZTH20_FUT_CBOT. Account: ******** | 2020-02-11 11:12:01.239 *" "NY -5/EST/-4 EDT, log attached." What will the charge be in this case? Manager of trade desk of broker requested analysis. |
Private File |
| [2020-02-13 09:31:21] |
| |
|
Cost will not be more than 20 USD. But one thing we can say with certainty now is this has nothing to do with any issue on the server. That particular order line is from a sub instance. So we need the trade activity file from the sub instance with the same date . The trade activity file you gave is from the main instance. We looked at that file, and it does not show any issue. You canceled the order a few minutes later and it was successful. 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 Date Time Of Last Edit: 2020-02-13 09:32:20
|
| [2020-02-13 15:15:57] |
| User379468 - Posts: 508 |
|
Attached. Please do address all 3 concerns in Post #1.
|
Private File |
| [2020-02-19 07:50:46] |
| |
|
We have examined this very closely and we simply do not have an explanation for why there was an order modification failure and why there is no additional text after: Order modification failed |
There should always be text after the |. We cannot see how this occurred. And furthermore because this was an active child order, this message should not have occurred either: Updated offset to 0.00781. But we can see the reason why this happened because the sub instance was not connected at the time of the order filled. We have implemented a solution for this. But it is a harmless message.These are the relevant messages indicating the order modification failure: ActivityType DateTime Symbol OrderActionSource InternalOrderID ServiceOrderID OrderType Quantity BuySell Price Price2 OrderStatus FillPrice FilledQuantity TradeAccount OpenClose ParentInternalOrderID PositionQuantity FillExecutionServiceID HighDuringPosition LowDuringPosition Note AccountBalance
Order 2020-02-11 11:11:10.952 ZTH20_FUT_CBOT ZTH20_FUT_CBOT 300 Trades #4 | User order modification. Updated offset to 0.00781. Requested Price: 108.00781. Requested Quantity: 3 3464 5494 Stop Limit 3 Buy 108 0.375/32 108 2.375/32 Pending Modify ** Close 3462 -4 2 Tgt -10+10+1, +20.twconfig Order 2020-02-11 11:11:10.953 ZTH20_FUT_CBOT Order modification failed | 3464 5494 Stop Limit 3 Buy 108 0.375/32 108 2.375/32 Open ** Close 3462 -4 2 Tgt -10+10+1, +20.twconfig There is no cost for this. We will just have to continue to contemplate this issue and see what we come up with later. But we need to make it clear this is not related to the TT order routing. 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 Date Time Of Last Edit: 2020-02-19 07:55:14
|
To post a message in this thread, you need to log in with your Sierra Chart account: