Trade Activity Log Analysis
- Determining the Origin of a New/Modified Order
- Support Assisted Trade Activity Log Analysis
- Possible Reasons for Unexpected Trading Issues
This page contains sections which describe various types of Trade Activity Log analysis procedures.
Determining the Origin of a New/Modified Order
If there is a question from an individual user or the trading/broker service, about the origin of either a non-simulated or simulated new order or order modification which may or may not have filled, then follow these instructions to make that determination.
These instructions will allow you to determine what particular Chart, Trading DOM or Automated Trading Study the order originated from or was modified from.
In the case of non-simulated trading, these instructions will allow you to determine whether the order originated from Sierra Chart or not.
- Select Trade >> Trade Activity Log on the main Sierra Chart menu.
- On the Trade Activity Log window, select Trade Activity from the top level menu.
- At the top left select All Activity to list both Orders and Fills.
- In the list of Symbols, select the symbol.
- In the list of Trade Accounts, select the particular Trade Account the order was submitted to. If you are not sure of the particular Trade Account, select All Accounts.
In the case of simulated trading within Sierra Chart, these accounts will begin with Sim#.
- In the Date Range to Display >> From Date box, enter a date which is earlier than the date of the order being questioned.
- Make sure Date Range to Display >> To >> Today is checked.
- In the list of Internal Order IDs make sure that All Internal Order IDs is selected.
- In the list of Notes, make sure All Notes is selected.
- Press the Apply button.
- Look at the DateTime column in the list on the Trade Activity tab, the OrderActionSource column and any other helpful columns, to locate the first line of the particular order in question. The time zone is going to be according to the global Time Zone setting in Sierra Chart.
- If you cannot find any evidence of the order in the log, then the order did not originate from Sierra Chart.
- When you find one or more lines for the order, look at the OrderActionSource column. Find the line where the OrderActionSource field contains the text "User order entry". Example: GCZ5 [C] 10 Min #2 | User order entry | Last: 1076.70. Attached Order.
- The line that contains the text "User order entry" in the OrderActionSource field, definitively indicates an order that has been submitted from Sierra Chart. This text also gives the particular Chart Number the order originated from. In this case chart #2.
- If the order is from an automated trading study, then the study that submitted the order will be given as well. You will also see the text Auto-trade: in the OrderActionSource field which indicates that this was an automated trade.
- Orders can also originate from sub-instances of Sierra Chart started through File >> New Instance. In this particular case, you will see the text Order from DTC client #4. Sierra Chart. 127.0.0.1 | Client text: Tag: for the OrderActionSource field. If the sub instance is not started, you can start it through File >> New Instance. You can then examine the Trade Activity Log in that sub instance for further details as to the origin of the order.
In this particular case the #4 does not indicate the sub instance number but a connection identifier for the sub instance. It continuously increments with each DTC Server connection with a client.
- The chart / Trading DOM that an order modification originated from is also given in the OrderActionSource field. If the order modification is from an automated trading study, then this field will also indicate this. Example: Auto-trade order modification: YMZ19[M] 1 Min #1 | Trade Management by Study. This indicates that the order modification originated from chart #1 and it was the Trade Management by Study study which modified the order.
- If you see an order line in the Trade Activity tab that contains the text | New order originated from external service, this indicates the first order line for an order received from an external trading service. This is an indication that the order originated from the external trading service and not within Sierra Chart.
Support Assisted Trade Activity Log Analysis
Under certain conditions Sierra Chart support can analyze the Trade >> Trade Activity Log to explain a particular live trading related situation (issue) that a user has a question about or had a problem with.
The procedure for this is explained below.
This information must be provided by the actual trader themselves so there is no misunderstanding about any of the information provided.
- Stop here if you have a question about simulated trading as we do not provide simulated trading analysis. If you are using Sierra Chart Trade Simulation Mode (Trade >> Trade Simulation Mode On) you may want to read the How Simulated Orders Are Filled section.
If you believe Sierra Chart did not do something properly with Trade Simulation Mode, then contact us with a brief description of the issue on the Support Board and we will take it from there and determine how best to help with it.
- Follow the instructions for Viewing Trade Historical Activity to locate the order and fill activity related to the particular trading situation you have a question about.
In most cases you will be able to determine the answer yourself by looking at the Trade Activity data. If this is the case, then stop here.
The Trade Activity Log is very useful to analyze precisely what has happened with a particular order and the source of all actions on that order.
To determine all of the actions on an order, be sure to select All Activity in the list box at the top of the Trade Activity Log, containing these options. In the log itself, the field Order Action Source indicates what the source of the action on the order was. This field also provides other useful subfields of information.
- There may be a cost for us to analyze this issue and it is billed at 60 USD per hour. Usually the analysis time will be about 20 minutes. If this is agreeable, put at least 20 USD on your Services Balance. The cost will also be waived if it is determined that the issue is related to some problem within Sierra Chart or related to an improvement that needs to be made within Sierra Chart. The cost is also waived if Sierra Chart support told you there is no cost for this.
Otherwise, there is a cost. Understand this type of analysis takes our time, and it is very involved analysis. We really do not want to get involved in these types of requests. Rarely is there anything found that would lead to any improvement in Sierra Chart.
- Follow the procedure in the Providing Trade Activity Log File to Support section to provide the Trade Activity Log file or files to Sierra Chart support.
These files are located in the \TradeActivityLogs subfolder in the Sierra Chart installation folder on your system.
There is a separate file for each day and Trade Account. The file name format for non-simulated trading is as follows: TradeActivityLog_YYYY-MM-DD_UTC.[TradeAccount].data. The file name format for simulated trading is as follows: TradeActivityLog_YYYY-MM-DD_UTC.[TradeAccount].simulated.data.
You will need to provide the files which contain data for the particular dates that you have a question about or Sierra Chart has specifically requested.
YYYY-MM-DD in the file name indicates the date. The time range is 00:00:00 through 23:59:59 UTC time. So Sierra Chart support will need the files covering the particular date and time range of the trading question.
These files can be attached as an email attachment or attached privately to the Support Board if using a Support Board posting. We do not keep these log files and will delete them when we are done looking at them.
- Tell us the Symbol you are trading. It is essential that we are provided this.
- Tell us the trading account identifier with your trading service that the order was entered from (account number). It is essential that we are provided this.
- Tell us the specific Date and Time of this trading related situation including the time zone. It is essential that we are provided this. We cannot be told a particular Date only. We need to know the specific Date and Time as precise as possible. We also need to know the Time Zone as well.
- We will need to know the Internal Order ID of the order. You can determine the Internal Order ID from the Trade Activity Log.
Go to the Trade >> Trade Activity Log >> Trade Activity tab and look at the Internal Order ID field for the order. For complete documentation to use the Trade Activity Log, refer to Viewing Historical Trade Activity.
Without this Internal Order ID we may not be able to answer the question because we will be unable to locate the order. As an alternative provide us the Service Order ID.
- Provide an accurate, brief and concise explanation of the particular trading related situation and your question. It is essential that we are provided this. If we do not sufficiently understand the issue, then we cannot help with the issue .
- We cannot change what has happened. We can only explain what you have experienced, and indicate the source of the issue to the best of our ability. There can be various causes of a trading related issue. A problem with the external trading service, a problem with network connectivity, an unusual circumstance that Sierra Chart was not able to properly handle, user error, or a user misunderstanding. Whatever the problem, we will do our best to identify it and explain what you have seen.
- Please allow up to 14 days for a response. This service should not be regarded as a service that can provide a fast answer.
Possible Reasons for Unexpected Trading Issues
- Potential Conditions Which Can Lead to Attached Orders Not Functioning As Expected in Live Trading
- Market Moving Quickly Beyond Stop Price Causing It to Become Invalid
- Automatic Replacement Market Order for Rejected Stop Attached Order
- Failure to Increase Quantity Due to Simultaneous Fill of Target/Stop Order Being Adjusted
- Failure to Increase Quantity Due Order Modification Rejection from Margin/Position Limits
- User Switching to Trade Simulation Mode before Attached Orders Sent
- Rejected Market Order When Using Flatten or Reverse Because of Position Limit Exceeded
- If you submitted order and it immediately cancels and does not fill, this can be because you set the Time in Force on the Trade Window to Immediate or Cancel. The solution is to use Day or Good till Canceled instead.
- There can be order rejections of new orders, and also order modifications which result, and orders either not working or the quantity or price of orders, not being as expected.
You can see rejections in the Trade Activity Log. In the case of a new order, look at the Order Action Source field for the rejection text and the Status field will be Error.
In the case of an order modification rejection status will still be Openbut look at the Order Action Source field for the description. Here is one such description:
Reject text: Insufficient margin Available margin: USD3121 Used margin: USD2000 Total portfolio margin including this order: USD3200 This order increases margin by USD1200
*Last modified Thursday, 16th July, 2020.