Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Sat, 18 May 2024 08:16:39 +0000
Post From: Server Side OCO Failure, and Incorrect Position/Missing Fill Data after Connection Reset
| [2016-10-21 04:00:49] |
| |
|
Sadly we realize the reason for this problem. The server-side OCO orders are not being passed through to the Rithmic API. We just sent this message over to Rithmic now about this: As you know Sierra Chart has used the R API + for about a couple of years now. The only thing used in that API is OCO orders. Although it has just come to our attention that since the beginning of July, the OCO orders have not been used through the API but yet brokers have been paying for this feature. The reason this happened is that there were some changes that were made that were never actually compiled into the external bridge program which interfaces to the API because of the problems we encountered compiling the bridge program which uses your API. This is one reason why we do not like API components. There was an unresolved conflict which was difficult to resolve due to an incompatibility and we still have yet to resolve it. This is one reason why we dislike Rithmic. It is always a struggle dealing with these external API components. We were not even aware that effectively the OCO orders had gotten disabled due to the changes and the failure to compile the bridge program due to the conflict. We recommend your broker changes your account over to CQG. 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: 2016-10-21 04:03:14
|