Support Board
Date/Time: Wed, 27 Nov 2024 16:37:54 +0000
Post From: Using Denali Futures Options Data With Trading Service
| [2022-07-25 11:09:37] |
| Sierra_Chart Engineering - Posts: 17195 |
|
We apologize for the long delay. We looked at the code and see how the solution was implemented to this. Once you submit an order for a symbol used as the Trade symbol for a Chart or Trade DOM, at that time the security definition data from CQG is requested. If you resubmit the the same order in about 2 to 5 seconds seconds later, it will go through. One thing we want to make clear is the way that the CQG Web API is designed in regards to having to obtain a numeric identifier for a symbol which varies from connection to connection, is a design that Sierra Chart very strongly disagrees with. It is a very poor design, and it is a mistake, to transfer this responsibility to the client program where a mistake can be made and can lead to serious consequences. This is something we have made clear in the documentation: Sierra Chart Does not Support External Service API Components: Recommended Protocol And that is not just CQG specific. We have seen this with other services like CTS, Transact, Tele-trader, CQG. None of which we support any longer other than CQG. There is also a similar issue we have seen with order IDs with the OEC API. 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, use the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2022-07-25 12:00:35
|