Login Page - Create Account

Support Board


Date/Time: Thu, 28 Nov 2024 21:47:22 +0000



Server-side 1-contract OCO orders counting as a 2-contract position?

View Count: 351

[2023-04-05 08:57:43]
User251043 - Posts: 46
Hi,

For MNQ I have set a position limit of 1 contract. With no positions (or other orders placed) I place an OCO order and both Teton and Trading Evaluator services tell me:

Teton CME Order Routing (Order reject). Info: Trade Order Error - Order with quantity 1 will cause symbol settings Position limit to be exceeded. Limit: 1. MaximumPotentialPositionQuantity: 2. Position: 0. Text: Tag: MNQprueba 1.twconfig. Internal Order ID: 6276. Service Order ID: 2020164. Symbol: MNQM23_FUT_CME. Account: XXXXX | 2023-04-05 09:58:27.181 *

Trading Evaluator (Order reject). Info: Trade Order Error - Order with quantity 1 will cause symbol settings Position limit to be exceeded. Limit: 1. MaximumPotentialPositionQuantity: 2. Position: 0. Text: Tag: MNQprueba 1.twconfig. Internal Order ID: 6344. Service Order ID: 4781996. Symbol: MNQM23. Account: XXXXX | 2023-04-05 10:38:52.246 *

Why does it consider an OCO order (Limit and Stop Limit) of 1 contract to be a Maximum potential position of 2? As OCO, they should be 1 contract position. What do I need to configure so it considers them just 1 position?

Thank you
[2023-04-05 10:06:49]
Sierra_Chart Engineering - Posts: 17206
Yes this is true. That will get rejected. There is no way around this. The position limit needs to be increased to 2.

If the OCO is associated with a parent order there would not be a rejection. But being there is no parent order there is a rejection.
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
[2023-04-05 12:59:15]
User251043 - Posts: 46
I understand it. Is there any way to create a ghost parent order or position so I can use the OCO without rejections? Maybe an OCO order client-side? Any other possibility to keep the position limit in 1? I usually work with OCO and I'd like to keep the position limit to 1 to prevent mistakes.

Thank you!

To post a message in this thread, you need to log in with your Sierra Chart account:

Login

Login Page - Create Account