Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Sun, 05 May 2024 23:30:47 +0000
Post From: No chart data
| [2014-03-12 20:34:57] |
| |
|
The ICE security definition request which is now required to use CTS T4 are working properly for us: CTS T4 - Sending security definition request for symbol TF.20140300.ICE_IN | 2014-03-12 16:29:51
CTS T4: Received 22 security definitions for underlying symbol RF_TAS | 2014-03-12 16:29:51 CTS T4: Received matching security definition for symbol TF.20140300.ICE_IN. Subscribing to data. | 2014-03-12 16:29:51 Although it does not surprise us, with what we see with security definition requests that some users may occasionally run into problems. We also have to handle the scenario of when a security definition is not found for a particular symbol. This is what makes the whole thing very complicated. This is a flawed design on the part of CTS T4. There is no other trading service or trading platform service that we work with, that works like this for outright futures contracts. They are making this very difficult. The whole design increases the likelihood of failures and ongoing issues. 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: 2014-03-12 20:36:11
|