Problem with data consistency

[StefanBelo.]

My app visually presents data on ladder so it is simply visible a problem with data consistency for runner tradedVolume.

To show visual data I need to know max traded volume, so here are some data. One can see that data fluctuates, as first interaction gave 31493.29, any other iteration should give bigger than that value, but it does not. For other data I did not notice this strange behavior.

MaximalTradedVolume: Leading Light, 31493.29
MaximalTradedVolume: Leading Light, 1468.28
MaximalTradedVolume: Leading Light, 31493.29
MaximalTradedVolume: Leading Light, 1468.28
MaximalTradedVolume: Leading Light, 1468.28
MaximalTradedVolume: Leading Light, 31682.44
MaximalTradedVolume: Leading Light, 31682.44
MaximalTradedVolume: Leading Light, 31682.44
MaximalTradedVolume: Leading Light, 31682.44
MaximalTradedVolume: Leading Light, 1468.28
MaximalTradedVolume: Leading Light, 1468.28
MaximalTradedVolume: Leading Light, 31682.44
MaximalTradedVolume: Leading Light, 31682.44
MaximalTradedVolume: Leading Light, 31682.44
MaximalTradedVolume: Leading Light, 31682.44
MaximalTradedVolume: Leading Light, 31682.44
MaximalTradedVolume: Leading Light, 31682.44
MaximalTradedVolume: Leading Light, 1468.28
MaximalTradedVolume: Leading Light, 1468.28
MaximalTradedVolume: Leading Light, 31682.44
MaximalTradedVolume: Leading Light, 31682.44
MaximalTradedVolume: Leading Light, 1468.28
MaximalTradedVolume: Leading Light, 31682.44
MaximalTradedVolume: Leading Light, 1468.28
MaximalTradedVolume: Leading Light, 31682.44
MaximalTradedVolume: Leading Light, 1468.28
MaximalTradedVolume: Leading Light, 31682.44
MaximalTradedVolume: Leading Light, 31682.44
MaximalTradedVolume: Leading Light, 31682.44
MaximalTradedVolume: Leading Light, 31682.44
MaximalTradedVolume: Leading Light, 31682.44

[StefanBelo.]

This problem is not yet fixed!

[BetfairDeveloperProgram]

HI StefanBelo,

We are investigating this issue and will provide an update when we have further information.

Kind Regards

Neil

[JayBee]

Yes, I can confirm this too.

The volume is jumping around like a sawtooth.

I can't do anything for a client until this is fixed.

[kawafan]

it also happen with the ex best offers and amount available.
e.g
sometimes , the best amount for back is having on each refresh.

46.33
46.33
46.33
46.40
46.33
46.33
46.40

I have set the blink event on changes and the its blinking without actually changing anything .

[StefanBelo.]

It seems you did not solve this problem. There are two types of this problem, and you can see it on my short video.

https://www.youtube.com/watch?v=gHDPLM5Y914

In the first case on Arsenal match for instance, marketBook.totalMatched fluctuates from bigger to lower value and around, from 1842.57 to 1837.50
The second case of data inconsistency can be seen in exchangePrices.tradedVolume.

API method listMarketBook once returns full list of traded volume, for instance 45 PriceSize data, and in every other 5-6 call it returns less number of data, for instance only 12 items in list/array of data.

You can see it at the end of video, when such error api behavior set wrong number for max traded volume.

[betdynamics]

It looks to me as if some of the servers in the server farm are returning old information - so some send new, some send old (could be wrong, but it sure looks that way)

[StefanBelo.]

Old API has the problem with total matched value, and they did not solve it, in my old app I should fixed it just by simply ignoring lower value, I think all others did the same.

With new api and ex.tradedVolume missing values. Well, there is too much missing values in returned data, so it is not "old value", it is like half of data is missing in some responses. That could be a clue to solve this problem.

[ForeTwo]

Why no response from BDP on this?

[JayBee]

Old API has the problem with total matched value, and they did not solve it, in my old app I should fixed it just by simply ignoring lower value, I think all others did the same.

With new api and ex.tradedVolume missing values. Well, there is too much missing values in returned data, so it is not "old value", it is like half of data is missing in some responses. That could be a clue to solve this problem.

This would not be a satisfactory solution for me.

My programs require second by second volume figures for charting purposes. The current bug does not give a "smooth" line. Instead I see a sawtooth pattern, which is useless as an indicator.

Imagine a bot that looks for a sudden move in volume. What is it going to do when the volume jumps around like this?

Does Betfair really think it is going to replace the old API with this broken one in just 7 days?

[StefanBelo.]

Last price traded has problem as well.

[JayBee]

Any update from Betfair???

Volume is still bouncing around like a groupy sitting on a rock star's noggin.

[BetfairDeveloperProgram]

Problem with data consistency

Hi All,

We have been investigating these issues in detail over the last few days

The below issue is being caused by rounding and currency fluctuations.

A fix will be deployed tomorrow morning at around 9am which should stabilize things:

it also happen with the ex best offers and amount available.
e.g
sometimes , the best amount for back is having on each refresh.

46.33
46.33
46.33
46.40
46.33
46.33
46.40

I have set the blink event on changes and the its blinking without actually changing anything .

We have been monitoring the more extreme traded volume issue over the last few days, but haven't seen this reoccur. Therefore, if you have captured an example, please provide us with the market details and the timestamp showing the point at which the data was logged. We can then examine our logs for a potential root cause.

Thanks for your feedback and patience!

Neil

[The other Geek]

Happening with Runner.lastPriceTraded today

[JayBee]

Problem still not fixed. I have sent a chart to support as proof.

What is happening is that previously traded volume is being removed and then added back later.

For those of us interested in volume traded this causes any charts depicting a volume timeseries to whipsaw up and down.