Posted: Oct 13, 2009 @ 02:18 AM             Msg. 1 of 3

Hi,

In Account DEMO151744 around twenty working orders were cancelled. This happened around 21:29pm, BST around 30 mins after FDAX closed. There are some details from my app's (based on Advanced Example) logfile below. These are OnOrderStateChanged() events. I dont believe that my app initiated these cancellations.

12/10/2009 21:29:22: OnOrderStateChanged(): Order Buy 1 FDAXZ9 STP 5872.0 GTC. Id = 36050566 State = Cancelled, Old State = Working

12/10/2009 21:29:22: OnOrderStateChanged(): Order Buy 1 FDAXZ9 LMT 5691.5 GTC. Id = 36050567 State = Cancelled, Old State = Working

I cant find any trace of these orders in the OrderControl panel.

Could you please let me know why this occured?

I also had plenty of other working orders in other contracts that managed to live overnight...

Thanks

Steve

---

S

Posted: Oct 13, 2009 @ 08:23 AM             Msg. 2 of 3

You are right, these GTC orders were not supposed to be cancelled automatically and your app didn't initiate cancellation.

We will check our simulation engine to find out what happened.

Sorry for inconvenience.

Posted: Oct 30, 2009 @ 03:22 PM             Msg. 3 of 3

Hi Serge,

Thanks for looking into it. Any news?

Meanwhile, I have the opposite issue now - orders not filling when they should - eg order 37017444 in account DEMO151744 sell FTSEZ9 limit 5010. I moved from an API trial account to a simultation account to be closer to the real thing, but I am still getting occasional errors like this one.

Does this kind of thing happen on the production server? I'm worried about a failed stop-loss on my production account losing real money.

(Its all great apart from these occasional gremlins!)

Thanks

Steve

---

S