Support Board
Date/Time: Thu, 06 Feb 2025 23:29:58 +0000
Attached orders disappearing
View Count: 801
| [2020-05-12 09:28:10] |
| Eisenhower - Posts: 30 |
|
I've been suffering intermittent connectivity issues which occasionally results in attached (stop / target) orders on open positions disappearing from my screen. The orders themselves apparently still remain active, but I can no longer see them or manage them through sierra chart. In one recent instance, after the stop/target on a position disappeared from my screen, I exited a position manually, only to come back later and find that one of the invisible attached orders had been executed, and I was now in a naked position I did not intend to have. Please help me figure out what is making these orders disappear from my charts so that I can continue to see and manage my positions. Thank you. |
| [2020-05-12 09:57:46] |
| |
|
The first step is to see if you see the orders in the Trade >> Trade Orders Window: Trading Information Windows: Trade Orders Window And also what your reporting is basically unheard of when using CQG. This is the kind of garbage we see when someone is using Interactive Brokers. 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 |
| [2020-05-12 10:04:00] |
| Eisenhower - Posts: 30 |
|
I'm using AMP / CQG from the message log: CQG WebSocket socket (1) | Close event error. Windows error code 10053: Eine bestehende Verbindung wurde softwaregesteuert durch den Hostcomputer abgebrochen. | 2020-05-12 05:10:25.923 * CQG WebSocket socket (1) | Socket gracefully closed by remote side. | 2020-05-12 05:10:25.923 CQG WebSocket socket (1) | CloseSocket call. | 2020-05-12 05:10:25.923 CQG WebSocket | Network socket for WebSocket has been closed by remote side or error. | 2020-05-12 05:10:25.923 CQG WebAPI | WebSocket closed. | 2020-05-12 05:10:25.923 Connection to the external service has been lost. | 2020-05-12 05:10:25.923 CQG WebSocket socket (1) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2020-05-12 05:10:25.923 CQG WebSocket socket (1) | Closed. | 2020-05-12 05:10:25.923 CQG WebSocket socket (0) | CloseSocket call. | 2020-05-12 05:10:25.937 CQG WebAPI | Disconnected. | 2020-05-12 05:10:25.937 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2020-05-12 05:10:25.937 CQG WebAPI | Connecting to server api.cqg.com | 2020-05-12 05:10:28.940 CQG WebSocket | Connecting to WebSocket server api.cqg.com:443 | 2020-05-12 05:10:28.940 CQG WebSocket socket (1) | Creating socket. Using TLS 1.2. | 2020-05-12 05:10:29.061 CQG WebSocket socket (1) | Connecting to IP: 195.166.124.165. | 2020-05-12 05:10:29.061 CQG WebSocket | Opening WebSocket. | 2020-05-12 05:10:29.087 CQG WebSocket | Sending WebSocket handshake. | 2020-05-12 05:10:29.087 CQG WebSocket | Server header | HTTP/1.1 101 Switching Protocols | 2020-05-12 05:10:29.244 CQG WebSocket | Server header | Connection: upgrade | 2020-05-12 05:10:29.244 CQG WebSocket | Server header | Sec-WebSocket-Accept: 3SjnXOQd/tLSkXejFdsCH+mHuzY= | 2020-05-12 05:10:29.244 CQG WebSocket | Server header | Server: WebSocket++/0.7.0 | 2020-05-12 05:10:29.244 CQG WebSocket | Server header | Upgrade: websocket | 2020-05-12 05:10:29.244 CQG WebSocket | Server header | | 2020-05-12 05:10:29.244 CQG WebSocket | Web socket state is now open. | 2020-05-12 05:10:29.244 CQG WebAPI | WebSocket connected. | 2020-05-12 05:10:29.244 CQG WebAPI | Sending market data logon message. | 2020-05-12 05:10:29.244 CQG WebAPI | Base Time: 2020-05-03T16:18:22. 2020-05-03 16:18:22 | 2020-05-12 05:10:29.848 CQG WebAPI | Logon successful. Session Token = Yc0g2Eb41yzIzQQxmMakNvmFvp2BynNALgNzjc9RKTo12WuyyRW27m6Q75de5z/0GCbPCAcBZLa | 2020-05-12 05:10:29.848 CQG WebAPI | Connected to data and trading server. | 2020-05-12 05:10:29.848 Triggering next historical data download in queue. | 2020-05-12 05:10:29.848 Triggering next historical data download in queue. | 2020-05-12 05:10:29.848 Triggering next historical data download in queue. | 2020-05-12 05:10:29.848 Triggering next historical data download in queue. | 2020-05-12 05:10:29.848 Updated verified funded futures trading account ending date to: 2020-06-11 09:10:30 | 2020-05-12 05:10:29.848 CQG WebAPI | Sending Trade Accounts request message. | 2020-05-12 05:10:29.861 CQG WebAPI | Brokerage name: AMP. Account Name: 114535 | 2020-05-12 05:10:29.938 CQG WebAPI | Sending collateral subscribe request. | 2020-05-12 05:10:29.938 Using SC exchange feed2. Symbol: F.US.EU6?## | 2020-05-12 05:10:30.066 CQG WebAPI | Sending symbol resolution request for F.US.EU6M20. ID: 633664 | 2020-05-12 05:10:30.066 CQG WebAPI | Requesting security definition data for: F.US.EU6M20. ID: 1 | 2020-05-12 05:10:30.066 Using SC exchange feed2. Symbol: F.US.EU6?## | 2020-05-12 05:10:30.066 Added historical Intraday data request for F.US.EU6M20 to the queue. | 2020-05-12 05:10:30.066 Intraday data recording state for symbol F.US.EU6M20 is set to download 'Pending'. | 2020-05-12 05:10:30.066 Triggering next historical data download in queue. | 2020-05-12 05:10:30.066 Delaying start of download for F.US.EU6M20 | 2020-05-12 05:10:30.067 Using SC exchange feed2. Symbol: F.US.CPE?## | 2020-05-12 05:10:30.067 CQG WebAPI | Starting real-time market data updates for: F.US.CPEN20. ID: 2 Service code: cqg | 2020-05-12 05:10:30.067 CQG WebAPI | Sending symbol resolution request for F.US.CPEN20. ID: 633665 | 2020-05-12 05:10:30.067 CQG WebAPI | Requesting security definition data for: F.US.CPEN20. ID: 2 | 2020-05-12 05:10:30.067 Using SC exchange feed2. Symbol: F.US.CPE?## | 2020-05-12 05:10:30.067 Added historical Intraday data request for F.US.CPEN20 to the queue. | 2020-05-12 05:10:30.067 Intraday data recording state for symbol F.US.CPEN20 is set to download 'Pending'. | 2020-05-12 05:10:30.067 Triggering next historical data download in queue. | 2020-05-12 05:10:30.067 Using SC exchange feed2. Symbol: F.US.NGE?## | 2020-05-12 05:10:30.071 CQG WebAPI | Starting real-time market data updates for: F.US.NGEM20. ID: 3 Service code: cqg | 2020-05-12 05:10:30.071 CQG WebAPI | Sending symbol resolution request for F.US.NGEM20. ID: 633666 | 2020-05-12 05:10:30.071 CQG WebAPI | Requesting security definition data for: F.US.NGEM20. ID: 3 | 2020-05-12 05:10:30.071 Using SC exchange feed2. Symbol: F.US.NGE?## | 2020-05-12 05:10:30.071 Added historical Intraday data request for F.US.NGEM20 to the queue. | 2020-05-12 05:10:30.071 Intraday data recording state for symbol F.US.NGEM20 is set to download 'Pending'. | 2020-05-12 05:10:30.071 Triggering next historical data download in queue. | 2020-05-12 05:10:30.071 Using SC exchange feed2. Symbol: F.US.EP?## | 2020-05-12 05:10:30.075 CQG WebAPI | Starting real-time market data updates for: F.US.EPM20. ID: 4 Service code: cqg | 2020-05-12 05:10:30.075 CQG WebAPI | Sending symbol resolution request for F.US.EPM20. ID: 633667 | 2020-05-12 05:10:30.075 CQG WebAPI | Requesting security definition data for: F.US.EPM20. ID: 4 | 2020-05-12 05:10:30.075 Using SC exchange feed2. Symbol: F.US.EP?## | 2020-05-12 05:10:30.075 Added historical Intraday data request for F.US.EPM20 to the queue. | 2020-05-12 05:10:30.075 Intraday data recording state for symbol F.US.EPM20 is set to download 'Pending'. | 2020-05-12 05:10:30.075 Triggering next historical data download in queue. | 2020-05-12 05:10:30.075 CQG WebAPI | Received symbol resolution report for symbol F.US.EU6M20. Search Symbol: F.US.EU6M20. Request ID: 633664. Contract ID: 1. | 2020-05-12 05:10:30.102 CQG WebAPI | Requesting market data for F.US.EU6M20 | 2020-05-12 05:10:30.102 CQG WebAPI | Received symbol resolution report for symbol F.US.CPEN20. Search Symbol: F.US.CPEN20. Request ID: 633665. Contract ID: 2. | 2020-05-12 05:10:30.102 CQG WebAPI | Requesting market data for F.US.CPEN20 | 2020-05-12 05:10:30.102 CQG WebAPI | Received symbol resolution report for symbol F.US.NGEM20. Search Symbol: F.US.NGEM20. Request ID: 633666. Contract ID: 3. | 2020-05-12 05:10:30.102 CQG WebAPI | Requesting market data for F.US.NGEM20 | 2020-05-12 05:10:30.102 CQG WebAPI | Received symbol resolution report for symbol F.US.EPM20. Search Symbol: F.US.EPM20. Request ID: 633667. Contract ID: 4. | 2020-05-12 05:10:30.133 CQG WebAPI | Requesting market data for F.US.EPM20 | 2020-05-12 05:10:30.133 Using SC exchange feed2. Symbol: F.US.MES?## | 2020-05-12 05:10:30.133 CQG WebAPI | Starting real-time market data updates for: F.US.MESM20. ID: 5 Service code: cqg | 2020-05-12 05:10:30.133 CQG WebAPI | Sending symbol resolution request for F.US.MESM20. ID: 633668 | 2020-05-12 05:10:30.133 CQG WebAPI | Requesting security definition data for: F.US.MESM20. ID: 5 | 2020-05-12 05:10:30.133 Using SC exchange feed2. Symbol: F.US.MES?## | 2020-05-12 05:10:30.133 Added historical Intraday data request for F.US.MESM20 to the queue. | 2020-05-12 05:10:30.133 Intraday data recording state for symbol F.US.MESM20 is set to download 'Pending'. | 2020-05-12 05:10:30.133 Triggering next historical data download in queue. | 2020-05-12 05:10:30.133 CQG WebAPI | Received symbol resolution report for symbol F.US.MESM20. Search Symbol: F.US.MESM20. Request ID: 633668. Contract ID: 5. | 2020-05-12 05:10:30.160 CQG WebAPI | Requesting market data for F.US.MESM20 | 2020-05-12 05:10:30.160 CQG WebAPI | Sending positions subscribe request. RequestID: 633669 | 2020-05-12 05:10:34.847 CQG WebAPI | Sending orders subscribe request. RequestID=633670 | 2020-05-12 05:10:34.847 Requesting market depth updates for: F.US.CPEN20 if supported. | 2020-05-12 05:10:34.847 CQG WebAPI | Requesting market data including full depth for F.US.CPEN20 | 2020-05-12 05:10:34.848 Requesting market depth updates for: F.US.EPM20 if supported. | 2020-05-12 05:10:34.848 CQG WebAPI | Requesting market data including full depth for F.US.EPM20 | 2020-05-12 05:10:34.848 Requesting market depth updates for: F.US.EU6M20 if supported. | 2020-05-12 05:10:34.848 CQG WebAPI | Requesting market data including full depth for F.US.EU6M20 | 2020-05-12 05:10:34.848 Requesting market depth updates for: F.US.MESM20 if supported. | 2020-05-12 05:10:34.848 CQG WebAPI | Requesting market data including full depth for F.US.MESM20 | 2020-05-12 05:10:34.848 Requesting market depth updates for: F.US.NGEM20 if supported. | 2020-05-12 05:10:34.848 CQG WebAPI | Requesting market data including full depth for F.US.NGEM20 | 2020-05-12 05:10:34.848 HD Request # 23 | Downloading Intraday chart data for F.US.EU6M20 to the file F.US.EU6M20.scid. Service: cqg | 2020-05-12 05:10:35.283 HD Request # 23 | Download start date-time: 2020-05-12 05:10:03.000 | 2020-05-12 05:10:35.283 HD Request # 23 | Using server: ds3.sierracharts.com port 10149 | 2020-05-12 05:10:35.283 Socket (2) | Creating socket. | 2020-05-12 05:10:35.283 Socket (2) | Connecting to IP: 65.182.172.42. | 2020-05-12 05:10:35.283 HD Request # 23 | Setting DTC encoding to Binary VLS | 2020-05-12 05:10:35.535 HD Request # 23 | Sending historical data logon request message. | 2020-05-12 05:10:35.535 HD Request # 23 | Requesting Intraday data. Start date-time: 2020-05-12 05:10:03. Record interval: 0. Symbol: F.US.EU6M20 | 2020-05-12 05:10:35.657 HD Request # 23 | Decompressing data. | 2020-05-12 05:10:35.778 HD Request # 23 | Receiving Intraday data for F.US.EU6M20 starting at 2020-05-12 05:10:03 | 2020-05-12 05:10:35.778 Socket (2) | CloseSocket call. | 2020-05-12 05:10:35.779 Socket (2) | Shutdown started. Waiting for graceful close. | 2020-05-12 05:10:35.779 Historical data download thread signaled to stop. | 2020-05-12 05:10:35.779 HD Request # 23 | Timestamp of first Intraday data file record written: 2020-05-12 05:10:05 | 2020-05-12 05:10:35.779 HD Request # 23 | Received 46 records from 2020-05-12 05:10:03.000 to 2020-05-12 05:10:31.010 (28.0 seconds) and wrote 41 records for F.US.EU6M20 | 2020-05-12 05:10:35.779 Added 1 Time and Sales records to Intraday data file for F.US.EU6M20 after download. | 2020-05-12 05:10:35.784 HD Request # 23 | Completion time: 0s | 2020-05-12 05:10:35.789 HD Request # 23 | Intraday data download complete for F.US.EU6M20. Unique request ID: 23 | 2020-05-12 05:10:35.789 Removing historical data download ID 23. | 2020-05-12 05:10:35.789 Real-time Intraday chart data file updates started for F.US.EU6M20 | 2020-05-12 05:10:35.789 Intraday chart data file opened for F.US.EU6M20 | 2020-05-12 05:10:35.789 HD Request # 23 | Enabling Intraday chart updating for symbol. | 2020-05-12 05:10:35.789 |
| [2020-05-12 12:39:45] |
| |
|
Our question was not answered. At this point we consider this support request resolved. We see you are using CQG and trading CME group markets. Please consider using the service as an alternative: Sierra Chart / Trading Technologies Futures 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-05-12 12:40:29
|
| [2020-05-12 16:36:13] |
| Eisenhower - Posts: 30 |
|
What question? You never asked one. I do not consider this issue resolved.
|
| [2020-05-12 20:51:42] |
| |
|
Maybe we were not entirely clear. In post #2 we said: The first step is to see if you see the orders in the Trade >> Trade Orders Window:
Trading Information Windows: Trade Orders Window So do you see the orders there? 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 |
| [2020-05-12 21:10:27] |
| Eisenhower - Posts: 30 |
|
Yes. The orders do appear in the trade orders window, and as I mentioned in the original post, they remained active and executed after disappearing from my screen. The issue is not about orders being canceled; the issue is that the orders stopped being displayed on my screen despite still being live.
|
| [2020-05-13 20:03:11] |
| |
|
Therefore, follow the instructions here to view those orders on the chart: Chart Trading and the Chart DOM: Viewing Orders and Trade Position on the Chart / Trade DOM The orders may not be within the current view of the price range of the chart. 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 |
| [2020-05-13 21:53:56] |
| Eisenhower - Posts: 30 |
|
Perhaps I was unclear. I will try to explain the situation again. I was trading from the chart, as I regularly do. The position and orders were displayed on the chart, and all were well within the price range of the chart. I saw them, I was able to modify them, etc. just as I always do. Then, I experienced an interruption in the data feed, and when the connection was reestablished, those orders disappeared from the chart. The position was still shown on the chart, but the attached target and stop orders were no longer being displayed. These orders remained active, remained within the price range of the chart, and then executed, all while no longer being displayed. The problem, once again, was these live orders, which had been displayed on my chart a moment earlier, were suddenly and inexplicably no longer being displayed. I will say again that this does not happen every time the connection breaks, but has occurred on on at least four separate occasions. It also caused me a trade error, when I manually exited an open position, believing the attached orders had been cancelled since they were no longer shown in the chart display, only to find out later that the invisible order was still live and then was executed, entering me into a new position while I was away from the desk. I hope you understand what I'm trying to say here but if not please ask me what it is I need to clarify. |
| [2020-05-13 21:57:54] |
| |
|
Check the Symbol and Trade Account of those orders in the Trade Orders Window which you do not see on the chart and expect to. They need to match those corresponding settings in the chart.
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 |
| [2020-05-13 22:12:33] |
| Eisenhower - Posts: 30 |
|
Yes of course symbol and account are correct, if they were not then the POSITION would not also still be displayed. As I said, the position was still being correctly displayed on the chart. The symbol was correct. The account was correct. The attached orders were within the displayed chart price range. They just disappeared from the chart after a connection to the data feed broke. As I also said, after the connection was reestablished I was again able to trade in this chart, enter new orders - which were displayed - but the previously entered orders that had disappeared, despite still remaining active, were no longer being displayed on the chart. |
| [2020-05-14 04:43:30] |
| |
|
Yes of course symbol and account are correct, if they were not then the POSITION would not also still be displayed. No that is not true.What is the exact symbol of those orders and the trade account of those orders and the symbol of the chart and the trade account the chart is set to. And also what is the Price1 field of those orders. We just do not know any of this information. You also need to then provide us an image of the chart. Once again here is the relevant full documentation: Chart Trading and the Chart DOM: Viewing Orders and Trade Position on the Chart / Trade DOM Please consider switching to the Sierra Chart order routing service: Sierra Chart / Trading Technologies Futures 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-05-14 04:51:13
|
| [2020-05-14 10:12:04] |
| Eisenhower - Posts: 30 |
|
Next time it happens I'll try to get a screenshot. But in all honesty I feel like I'm running around in circles here and this certainly does not make me want to buy yet another "service" from sierrachart |
| [2020-05-14 10:21:16] |
| |
|
You are not using a service from Sierra Chart. You are using CQG! Also, this whole thing is very unusual anyway. We have identified the relevant fields which can cause a problem. So you have the ability to determine what the issue is. We do not know. The reason we developed the Sierra Chart order routing service is to solve all of the problems we see with all of these external services and provide a unified way of doing things. Refer to: Year 2019 for Sierra Chart 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: