Login Page - Create Account

Support Board


Date/Time: Fri, 29 Mar 2024 05:10:39 +0000



LMAX trades

View Count: 902

[2018-10-01 19:11:00]
User518169 - Posts: 9
Trade actions taken on the LMAX web platform do not get effected on Sierra platform. The impact of this is that an order that was closed on the web platform (or mobile platform) remains on Sierra and when flattening it on Sierra, it opens an opposite trade on LMAX.

This is with reference to my Demo account and live account.

Is this normal?
[2018-10-01 23:43:50]
Sierra Chart Engineering - Posts: 104368
This should not be the case but it is important to understand how the Positions are determined. Refer to:
LMAX Trading Service: How Current Trade Positions Are Determined


Once you read that, that may answer the problem.

Otherwise, what we want to do is to have Sierra Chart running and then on the LMAX web platform, enter a limit order and check to see that you see it in Sierra Chart through Trade >> Trade Orders and Positions >> Orders. You definitely should. If not we need to look into this.
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: 2018-10-01 23:44:07
[2018-10-02 13:16:02]
User518169 - Posts: 9
Good day

1) Orders placed on the web platform do not appear here Trade >> Trade Orders and Positions >> Orders either.

2) I placed a market order (on Sierra) and this is the Log (Note that this order was transmitted successfully to LMAX despite this Log):

LMAX Demo Trading - DTC order update (Order reject). Info: LMAX order update (Rejected). Text: OUTSIDE_ALLOWED_PRICE_RANGE. Text: Attached order. Parent: 2340. Internal Order ID: 2341. Service Order ID: 218268. Symbol: GBPAUD | 2018-10-02 09:01:45 *
LMAX Demo Trading - DTC order update (Order reject). Info: LMAX order update (Rejected). Text: Illegal stop price for stop order. Text: Attached order. Parent: 2340. Internal Order ID: 2342. Service Order ID: 218269. Symbol: GBPAUD | 2018-10-02 09:01:46 *
[2018-10-02 18:41:47]
Sierra Chart Engineering - Posts: 104368

1) Orders placed on the web platform do not appear here Trade >> Trade Orders and Positions >> Orders either.
Not sure why this is the case . We thought we could look into this from our side but thinking about it, you really need to ask LMAX about this. Give them your LMAX demo account number. But make sure that you are looking at the very same account in Sierra Chart. You can see the account number on the Trade Window:
http://www.sierrachart.com/index.php?page=doc/TradeWindow.html#SelectingTradeAccount




2) I placed a market order (on Sierra) and this is the Log (Note that this order was transmitted successfully to LMAX despite this Log):

LMAX Demo Trading - DTC order update (Order reject). Info: LMAX order update (Rejected). Text: OUTSIDE_ALLOWED_PRICE_RANGE. Text: Attached order. Parent: 2340. Internal Order ID: 2341. Service Order ID: 218268. Symbol: GBPAUD | 2018-10-02 09:01:45 *
LMAX Demo Trading - DTC order update (Order reject). Info: LMAX order update (Rejected). Text: Illegal stop price for stop order. Text: Attached order. Parent: 2340. Internal Order ID: 2342. Service Order ID: 218269. Symbol: GBPAUD | 2018-10-02 09:01:46 *
What is happening is the attached orders are getting rejected by LMAX due to the prices. You need to ask them why. We do not observe this from our side in a test. In your case the parent order is still getting successfully processed by LMAX.
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: 2018-10-02 18:48:08
[2018-10-03 07:41:40]
User518169 - Posts: 9
Is this the reason why actions taken on LMAX do not get transmitted to Sierra?
[2018-10-03 08:13:46]
Sierra Chart Engineering - Posts: 104368
Is this the reason why actions taken on LMAX do not get transmitted to Sierra?
What reason is this? We do not know what you are referring to. The only logical reason we can think of is that you are looking at different account numbers through the LMAX web trading as compared to Sierra Chart.

We are going to run a test ourselves later today and see what we determine.

We also have never heard of an issue like this with Live LMAX trading. Or actually even demo trading other than this.
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: 2018-10-03 08:14:23
[2018-10-03 12:32:32]
User518169 - Posts: 9
I agree with you. I have been able to execute and close trades on either LMAX platform or Sierra and the actions would be mirrored successfully. This issue is new to me.

Just to clarify, the order, is in fact, accepted and transmitted to LMAX from Sierra despite the the "Rejection" log (Maybe the order is filled at a different price). The issue is as follows:

1) I execute a Buy market order on Sierra and it immediately reflects on the LMAX (and displays the rejection error message).
2) I close that very same order, this time, directly on LMAX web platform but it does not get closed on Sierra (it remains open on Sierra and closed on LMAX).
3) I then close it on Sierra and what happens is that it gets closed on Sierra (and again, displays a rejection error message) but opens an opposite trade (a Sell Market order) on LMAX web platform.

In a nutshell:
1) There is a rejection error message (but the order transmitted from Sierra).
2) There is a one-way transmission from Sierra to LMAX (no transmission from LMAX to Sierra)

This phenomenon is occurring on both my accounts (Live and Demo) individually
[2018-10-03 17:37:47]
Sierra Chart Engineering - Posts: 104368
You need to ask LMAX about those rejection messages. They are for the Attached Orders. Not the child order. Also we cannot duplicate any type of rejection of the Attached Orders.


1) I execute a Buy market order on Sierra and it immediately reflects on the LMAX (and displays the rejection error message).
2) I close that very same order, this time, directly on LMAX web platform but it does not get closed on Sierra (it remains open on Sierra and closed on LMAX).
3) I then close it on Sierra and what happens is that it gets closed on Sierra (and again, displays a rejection error message) but opens an opposite trade (a Sell Market order) on LMAX web platform.
We think the problem may relate to the Position Quantity: Refer to:
LMAX Trading Service: How Current Trade Positions Are Determined

However, we are going to be testing this today and see if we notice the same issue.

1) There is a rejection error message (but the order transmitted from Sierra).
It is the child orders getting rejected. Not the parent order. There is a misunderstanding on your part. You cannot have a rejection but yet still have a processed order. This is an impossibility.


2) There is a one-way transmission from Sierra to LMAX (no transmission from LMAX to Sierra)
We will look into this.

3) I then close it on Sierra and what happens is that it gets closed on Sierra (and again, displays a rejection error message)
Also if you are getting this rejection it probably is for the Attached Orders for unknown reasons. You should not be closing a position using Attached Orders. So uncheck the Use Attached Orders option on the Trade Window. You do not want to close a position using a parent order and two child orders.
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: 2018-10-03 17:39:45
[2018-10-03 19:15:06]
User518169 - Posts: 9
I have managed to resolve the issue regarding the errors. The stop and limit protection orders were too far out.

The one way transmission problem still persists. See, attached, response from LMAX
imageResponse from LMAX.jpg / V - Attached On 2018-10-03 19:13:23 UTC - Size: 616.61 KB - 233 views
[2018-10-03 19:34:38]
Sierra Chart Engineering - Posts: 104368

The one way transmission problem still persists. See, attached, response from LMAX
We are looking into this today. It is possible that this is a new issue related the recent development related to solving an order ID matching issue one user had with LMAX.
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: 2018-10-03 19:37:18
[2018-10-03 19:57:21]
User749205 - Posts: 38
Hope it's ok to chime in here, as you're currently testing, I'm also experiencing LMAX issues that may be related.

I can open one position with its accompanying child orders, I then put a second order in, which when triggered merges the two positions (I get the average position of both entries on one line), and the second positions child orders do not get executed, so that were price to move against me, the first trades stop might get hit but for the second I'd stay exposed until I manually closed it.

I'd be grateful if you could test opening two positions each with child orders.
[2018-10-04 03:56:19]
Sierra Chart Engineering - Posts: 104368
In regards to the issue of Sierra Chart not processing the LMAX execution reports for orders entered outside of Sierra Chart, we have identified the problem where the trade account was not being assigned to the externally received order and that is what was leading to the problem. This is now resolved.

All of the missing order fills are in the process of being downloaded.

But we notice that this is creating a significant processing load at times and we cannot allow that at this time. We will need to finish with this over the weekend. And we are not sure how far back we can go on the live system for order fills. Possibly only seven days.



When the missing fills are added in, to get the them, what you need to do is follow the instructions here to display the order fills for the last 45 days:
Trade Activity Log: Viewing Historical Trade Activity

And then clear them by selecting them and selecting Edit >> Delete Trade Activity Entry. After this reconnect to the data feed.

It will be best to wait till we finish getting them all over the weekend.


----
For some background as to why this issue occurred. It related to changes to the account number handling to provide faster lookup of orders. And for externally received orders it was not getting set in the case of LMAX.

The issue is only very recent in the live trading environment and LMAX demo environment it goes back to August 24.

Normally an issue like this is of minimal consequence but because positions are calculated off order fills, it does affect position reporting in Sierra Chart since LMAX does not provide any position reporting over FIX.
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: 2018-10-04 04:10:41
[2018-10-04 03:57:09]
Sierra Chart Engineering - Posts: 104368
In regards to post #11 we will do some testing for this now but this looks quite unrelated. Also it is normal for there to be just a single position line.
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
[2018-10-04 04:01:02]
Sierra Chart Engineering - Posts: 104368
In regards to post 11, we cannot reproduce any problem like this but of course there is just going to be one position line showing the average price.

The two sets of limit orders and stop orders did get executed/canceled as expected when the price touched one of them.
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:

Login

Login Page - Create Account