Something Screwy on 90D.JUN10.LOW

At 5.30pm I had a sell position of 8 @ .5000. At 7.00pm a sale is shown as having occurred at 6.31pm for .5000 yet, strangely, I still 8 @ .5000. How come, I am at the top of the sell list so I am, in effect, "first cab off the rank", a sale is showing as having occurred at the price I'm offering and I still have the same number of stock?

The chart, however, shows a last sale at 3.46pm for .5290.
The API shows 0.5290 30 15.8700 2010-03-23 15:46:17+13:00
followed by 0.5290 30 15.8700 2010-03-23 15:47:13+13:00

My Portfolio shows a last price of .5000.

What the hell is going on?

Edit: A similar thing happened over the weekend on either this stock or 90D.JUN10.VLOW.



Edited 2 time(s). Last edit at 03/23/2010 07:38PM by ORACLE.

Hi Oracle,

In our logs, I can see that you shorted 8 @ .5 for 90D.JUN10.LOW - as the result of a passive trade (ie an order of yours was matched)

Also, there were no trades on that stock at 7pm (or even times close to 7pm)

I imagine that the confusion is caused by the same issue that has caused some charts to display incorrect data. The charts are powered by data as returned by the api call, so it that's wrong then the charts are wrong.

That issue is being looked at now, I reckon I know what is going on (and it is only the stocks with lots of trades) - and if my hunch is correct we should have a fix for that out shortly.

Of course, that issue does not affect the actual trading at all, it is just not showing all the trades correctly in some stocks - but as as say, a fix for that is due out v. soon.

Hi iTeam and thanks for the reply. Re-reading my post I see that I should have stated where I saw the sale at 6.31pm for .5000. It was in the Contract Info porting of Contract Details and it was at 7.00pm when I saw it. I couldn't find supporting evidence of a transaction at 6.31 from either the chart of or pipe42's API Interface.

The Contract Info made it look as though a transaction/s had occurred that should have meant my sell order would be satisfied but it wasn't. I had thought that my machine may have cached from an earlier period so went through the process of clearing the cache, history etc, but that made no difference so the only option left was the Bug Report.