Posted: Sep 12, 2007 @ 02:48 AM             Msg. 1 of 12

Previously, I have used the OEC Trader Demo for manual execution and have vitnessed that on occasion when I'm in a trade the system would exit my trade at 12:30 ET without me initiating it. I had communcated this problem via online chat. However, it appears that it has not been addressed, as I explain next.

Recently I have been live simulating my auto-trading system using my API account. On Tuesday (yesterday) I had three strategies running; one had me long 1 contract ES, another also long 1 ES and the third long 1 contract ER2. At 12:30 ET one ES contract and the ER2 contract were liquidated; which is not part of my strategies. My auto-trading system has been run with another broker and has performed as required and from my previous experience with OEC Trader Demo, I am confident that the uninitiated trade liquidations are inherent to your system. I'm hoping something can be done about this.

Posted: Sep 12, 2007 @ 01:51 PM             Msg. 2 of 12

assuming you are using username RXiaojin wang and account DEMO013403, I have checked - all orders were sent from the same IP address by same application named OECDemo v 1.0.2802.42003, which clearly is not the our OEC Trader Demo application

there were no admin interaction and no other source of orders - so please check your auto-trading system.

please let us know if you are using other username/account, or have specific order number that you believe was not sent by your app.

Posted: May 16, 2008 @ 07:08 AM             Msg. 3 of 12

I need to readdress this issue. I refer here specifically to the simulation account (I have not witnessed this problem on the live account).

A number of times in the last few weeks, trades have been taken which have not been initiated by my auto-trading system. It appears that stops that have been placed by my trading system are elected regardless of relevant price action. This always occurs at 2:30PM ET. For example, yesterday (5/15) one of my trading strategies which was trading the ESM8 had placed a sell stop at around 1408.25, however at 2:30PM ET the order was filled at 1415.25 which is the level the price was at that time.

By the way, I have run my strategies with your demo account and also simultaneously run the same strategies using the same software (apart from the brokerage linkage component) with another brokerage. The OEC account initiated unwanted orders as described above but this did not happen with the other brokerage. So, I am definitely convinced that the problem is at your end (with the simulation account).

I hope this can be resolved as this problem has persisted for many months.

The information that you provided concerning my account in your previous post was correct.

In case you need to know: I am using Wealth-Lab Developer (WLD) (www.wealth-lab.com) as my auto-trading system. My trading stratgies are written using the Wealth-Lab scripting language. My connection to the OEC brokerage is via COM using a specially written adapter. I can connect to other brokerages simply by using other adapters. WLD also provides backtesting of my strategies which allows conformation of performance before live or simulated trading.

Again, I hope this issue can be resolved soon.

Posted: May 16, 2008 @ 08:50 AM             Msg. 4 of 12

I've checked orders for 05/15, and they are all sent from the IP of 71.59.214.6 - so all orders are sent by your application.

However, the order 12710267 (Sell 1 ESM8 STP 1408.25 at 2:20 pm), which was filled at 2:30 at 1415.25 looks strange - it might be a price fluctuaction or simulation engine problem.

We will research that issue further and will let you know the outcome as soon as possible.

Posted: May 21, 2008 @ 07:52 AM             Msg. 5 of 12

Any progress with this problem?

Yesterday (5/20), the problem manifested itself again. One strategy that I was auto-trading was short one contract ER2M8, a reversal buy stop had been placed at 735.6 but at 2:30 PM ET the stop was elected when the price was at 730.1 (this was the resultant fill price).

Surely a fundamental, consistently reoccuring issue like this could be fixed soon?

Posted: May 21, 2008 @ 08:31 AM             Msg. 6 of 12

We are still researching this - looks like a problem in the simulation engine.

Posted: Sep 23, 2008 @ 11:09 AM             Msg. 7 of 12

This problem has not yet been resolved. Yesterday and Friday my sitting EMD stop orders where elected at 2:30 PM ET even though price was nowhere near the stop level.

It has been over a year since I first brought this issue to your attention. (And all during that time I've been charged $25/month for a severely incapacitated simulator). Can you finally do something about this?

Posted: Oct 13, 2008 @ 03:26 PM             Msg. 8 of 12

I also noticed that stop orders are incorrectly triggered. I posted somewhere else but I copied my post here:

--------------------------------------------------
I found a potential bug in stop order handling. Sometimes a stoploss order which should not be triggered was mistakenly triggered and executed. Here is an example:

14:15:00 #18131270 Create Sell 1 YMZ8 STP 8655
14:15:00 Sent
14:15:00 Working #1168691
14:30:01 #18132891 Modify Sell 1 YMZ8 MKT
14:30:01 Modified Auto-Updated
14:30:01 Completed
14:30 Fill 1 @8946

As you can see, a sell stop order at 8655 was mistakenly triggered at 8946, which is quite far from the stop price. Does this mean you data has spikes outside of the market?
-------------------------------

Posted: Oct 13, 2008 @ 04:26 PM             Msg. 9 of 12

We are still working on this issue.

Posted: Oct 22, 2008 @ 03:18 PM             Msg. 10 of 12

"We are still working on this issue."

One must really call into question your resolve to solving this problem:

Today, I had a sitting stop buy order on the ES at 933.50
elected at a price of 915.50. The time was 2:30 ET (as always).

Posted: Oct 22, 2008 @ 03:33 PM             Msg. 11 of 12

Our developers are still investigating the issue.
Sorry for inconvenience.

Posted: Jan 15, 2009 @ 05:29 AM             Msg. 12 of 12

The status of this problem has not changed in the three months since SergeK's last post. I trust work is still "progressing" on this problem?

For example, today I had a buy stop on EMDH9 at the 503 level filled at the price of 501. This occured at 2:30 PM ET (as usual).