Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Tue, 23 Apr 2024 14:24:08 +0000
Trade Execution Issue
View Count: 545
| [2020-06-16 01:01:58] |
| User94606 - Posts: 327 |
|
On June 15, 2020, I executed a trade on NQ (2 contracts). I used attached orders with a 10-tick stop. The buy order for 2 contracts executed (1@9540.25 and 1@9540.50) at 09:32:17 EST and I got stopped out (1@9537.75) of only 1 contract at 09:32:18 for $50 loss. I did not realized that I was only stopped of 1 contract until 1 minute later that I realized that I still had an active contract. I ended up closing the 2nd contract manually for a loss of $745 (1@9503.25). Can you help explain why the 2nd contract was not closed as part of the attached order stop loss at 09:32:18 EST? I am attaching the Trade Activity Log for your reference. Date Time Of Last Edit: 2020-06-16 03:28:34
|
Private File |
| [2020-06-17 03:22:59] |
| User94606 - Posts: 327 |
|
Any updates?
|
| [2020-06-26 03:14:50] |
| User94606 - Posts: 327 |
|
Any updates?
|
| [2020-06-26 05:47:25] |
| |
|
We looked at that log but it does not have the information needed. This is the information that is needed: Trade Activity Log Analysis: Support Assisted Trade Activity Log Analysis We think you can analyze this yourself. Go through the Trade Activity Log and see what happened to the Stop Attached Order. In general what you describe, usually is the result of a Stop Attached Order getting rejected when it is sent or the modification to increase its quantity. 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: 2020-06-26 05:47:48
|
To post a message in this thread, you need to log in with your Sierra Chart account: