Home >> Support Board

Support Board

Date/Time: Fri, 18 Oct 2024 10:13:05 +0000

How to Post a Message for Support

Post From: Chart lag, trading data disconnections, unable to modify orders, order overfills

[2024-07-14 21:14:14] Link To Thread - Link To Post [Go To First Post]
skyfly93 - Posts: 34
OK I've set up another installation of Sierra Chart with the Data/Trade service settings set to SC Data-All Services. With this Data/Trade service, I'm unable to take trades in it because my Apex Rithmic accounts do not show up. The main issues I'm trying to solve are documented in the Trade Service Log, which I attached, and I had copy pasted the different errors I'm getting which are more related to order entry and management, failed modifications, disconnecting from trading service and then reconnecting, overfill errors, trade order error and timing out, requesting order status for non-responsive order which can take up to 62+ seconds of time out, and etc. 2024-07-11 08:44:47.750 \| Order modification failed (InternalOrderID) \| Unable to modify order because it is no longer working. Internal Order ID: 107752. Service Order ID: 1605036644. Symbol: MNQU4.CME. Account: APEX-XXXXX-91 * 2024-07-11 08:52:21.631 \| Notice - An overfill UpdateOrder call has occurred. Overfill Quantity: 32766. Total filled quantity: 1. Order quantity: 1 \| Symbol: MNQU4.CME \| TradeAccount: APEX-XXXXX-91 \| InternalOrderID: 107895 \| ServiceOrderID: 1605090271 \| Current Status: Filled * 2024-07-11 09:35:59.555 \| Not connected to the Trading service. Select 'File >> Connect to Data Feed' to connect. You may need to reconnect with 'File >> Disconnect' and 'File >> Connect to Data Feed' * \| Number times message added: 2 2024-07-11 09:36:56.569 \| Requesting order status for non-responsive order. Time since last action: 56.8 seconds \| Symbol: MNQU4.CME \| TradeAccount: APEX-XXXXX-83 \| InternalOrderID: 109926 \| Current Status: Order Sent * 2024-07-11 09:37:16.840 \| Requesting order status for non-responsive order. Time since last action: 62.8 seconds \| Symbol: MNQU4.CME \| TradeAccount: APEX-XXXXX-90 \| InternalOrderID: 109816 \| Current Status: Order Sent * 2024-07-11 09:37:26.744 \| Trade Order Error - Order timed-out waiting for response from service/exchange server. Internal Order ID: 109671. Service Order ID: (none). Symbol: MNQU4.CME. Account: APEX-30791-91 * 2024-07-11 09:38:07.587 \| Rithmic Direct - DTC \| Requesting historical account balances for account APEX-XXXXX-83. Start date-time UTC: 2024-03-09 16:38:07 2024-07-11 09:38:07.596 \| Trading server did not acknowledge new order \| Symbol: MESU4.CME \| TradeAccount: APEX-XXXXX-91 \| InternalOrderID: 109941 \| Current Status: Order Sent * 2024-07-11 09:41:03.253 \| Order modification failed (InternalOrderID) \| Unable to modify order because it is no longer working. Internal Order ID: 110139. Service Order ID: (none). Symbol: MESU4.CME. Account: APEX-XXXXX-86 * 2024-07-11 09:44:01.229 \| Not connected to the Trading service. Select 'File >> Connect to Data Feed' to connect. You may need to reconnect with 'File >> Disconnect' and 'File >> Connect to Data Feed' * \| Number times message added: 2 2024-07-11 09:45:00.752 \| Requesting order status for non-responsive order. Time since last action: 60.3 seconds \| Symbol: MNQU4.CME \| TradeAccount: APEX-30791-83 \| InternalOrderID: 110464 \| Current Status: Order Sent * 2024-07-11 09:45:18.462 \| Rithmic Direct - DTC \| Requesting trade accounts from server. 2024-07-11 09:45:26.039 \| Trading server did not acknowledge new order \| Symbol: MNQU4.CME \| TradeAccount: APEX-XXXXX-83 \| InternalOrderID: 110464 \| Current Status: Order Sent * 2024-07-11 09:45:26.040 \| Rithmic Direct - DTC \| Requesting historical account balances for account APEX-XXXXX-90. Start date-time UTC: 2024-03-09 16:45:26 When you say "see if you have any data feed issues in that instance" what exactly should I be observing? The issues I mentioned typically occur when volatility and or volume pick up, but not referring to news event. The two documented times that it happened last week was on July 11 between 8 am - 9:51 am PST and July 12 between 10:37 am - 12:43 pm PST, both times you can see had volatility increase on ES and NQ.