Version 7.1.0.6

Since using the new version I have experienced a couple of problems I wasn't having before.

1.  API connection going down repeatedly over the weekend.  I note tdadba was seeing the program shut itself down - which I'm pretty sure would just have been the API connection.  If you are reading this tdadba, has going back to the previous version solved the problem?  I will probably do the same for now, although it could just be a coincidence; i.e. perhaps Betfair had persistent API problems just after version 7.1.0.6 came on stream.

2.  My current bets refresh time has started increasing dramatically as my number of matched bets on a market increases; from about 0.5 sec to 3 secs.  Again, I guess it could just be an API problem, but I'm thinking that it may be more than a coincidence that this problem arose only when I used the new version.

Anyway, I thought I would report in to back up tdadba's experience in the hope that it might help identify and solve the problem.

Hi Mark,

Ah I discovered the problem for the India test. My default setting only sought matches one day ahead.
However the last test at Calcutta I'm reasonably sure it didn't find the match on the day
it was being played as I sent a post to "suggestions", anyway only a minor point.
Thanks
R

You are correct, however, India creamed West Indies in the 1st test and the match finished with 2 days to spare, which explains why you could not find it.

1.  API connection going down repeatedly over the weekend.  I note tdadba was seeing the program shut itself down - which I'm pretty sure would just have been the API connection.  If you are reading this tdadba, has going back to the previous version solved the problem?  I will probably do the same for now, although it could just be a coincidence; i.e. perhaps Betfair had persistent API problems just after version 7.1.0.6 came on stream.

Orzola, I might disappoint you, but we really, really cannot influence the API being up or down. The API is a service which is run by BetFair. It might be a coincidence that they are having problems right as we made the update, but it's just what it is - a coincidence.

2.  My current bets refresh time has started increasing dramatically as my number of matched bets on a market increases; from about 0.5 sec to 3 secs.  Again, I guess it could just be an API problem, but I'm thinking that it may be more than a coincidence that this problem arose only when I used the new version.

And again, the time it takes to refresh your bets (or rather download them from the BF server) has nothing to do with the new version. I'm sure if you opened the older version and measured the time in question, it would turn out to be the same as with the new version.

Anyway, I thought I would report in to back up tdadba's experience in the hope that it might help identify and solve the problem.

Right, looking into it.

No, Im doing the manual search...

Can you please confirm that MF Pro crashes when you are performing a manual search in Market Locator?

Orzola, since you are backing up tdadba's post, does it mean that you too are having the exact same problem?

Hi Oxa

I was just referring to tdadba's post:

"After the update my MF begin to close by itself several times a day, so I prefer to downgrade it... Could be a bug?"

After the update I was repeatedly getting the warning that the program was going to shut itself down due to repeated need to log back on.  I assume that was what was closing tdadba's bot down.

I realise that you can't control the betfair API (and you haven't disappointed me yet).  Hopefully it is a coincidence, since I would like to use the latest version of the program.  But from my background of inadequate IT/programming knowledge, it seemed like it could be more than that.  My trigger had been running smoothly for months and then I suddenly got major and persistent problems the weekend after the upgrade.

I will test further later in the week and let you know if I get similar issues.

I did't have any issues with the Market Locator, but then I do mine manually.

Hi,
Just tried to download without success another cricket match currently in play between Sri Lanka and New Zealand and held at the Hambantota ground in Sri Lanka according to the reliable Cricinfo site. For some unknown reason Betfair still shows the Calcutta time but that's another matter.
This is another one to consider adding to the mlocator.
Thanks
R

Hi,
Just tried to download without success another cricket match currently in play between Sri Lanka and New Zealand and held at the Hambantota ground in Sri Lanka according to the reliable Cricinfo site. For some unknown reason Betfair still shows the Calcutta time but that's another matter.
This is another one to consider adding to the mlocator.
Thanks
R

Hi racepro
From time to time there are markets which are not categorised under any country. We had a similar situation several weeks ago with the UEFA football markets. Although these markets might not be shown using the Locator tool because a country must be specified, you can still find them manually by navigating the Event Tree in the All Markets tab. I managed to catch the cricket match in question just before it finished (screenshot).

In this situation, where there is nothing from Locator, I would quickly check Betfair website, and bring up a market. On the left side on the website market screen, you can see mostly where Betfair have hidden it. Then it is just a matter of switching to MFP and manually loading the market from All Markets now you know where it is hidden.
Hope this helps.

Important Update:

Thanks to a notification sent by one of our customers, I have realised that version 7.1.0.8 can be writing some log information to a file which can grow in size and take up space on your disk. This log information was needed for debugging the program, it accidentally remained in the code.

I’ve just made a fix, you will notice an update notification come up in MF Pro when you next log in. Please install it to clear the log file and prevent it from appearing there again.

Many apologies for this inconvenience!

Thanks Mark,
I know for next time, although I do remember Oxa mentioning this before.
It has now sunk in
R

Important Update:

Thanks to a notification sent by one of our customers, I have realised that version 7.1.0.8 can be writing some log information to a file which can grow in size and take up space on your disk. This log information was needed for debugging the program, it accidentally remained in the code.

I’ve just made a fix, you will notice an update notification come up in MF Pro when you next log in. Please install it to clear the log file and prevent it from appearing there again.

Many apologies for this inconvenience!

Does this apply to the Time Machine file, or just the standard program?  My Time Machine opening screen is suggesting I download the latest version.

Rubold, I will make the update of Time Machine later, although this very problem (with the log file) does not happen when in Time Machine mode.

This growing log file, was that in the previses version too? I am running 7.0.0.47 and I need to restart it almost every day - due to that the software stop placing bet, but no errors appear.
I noticed that it's often happening when my statement of settled games seems not to be updating, which could explain way it stop placing bets.

Tupp, the log file was present only in v. 7.1.0.6.

However, there was a bug in v. 7.0.0.47 and older versions that resulted in the possibility of one of the bets not included in the real account statement: see the list of fixed bugs in the beginning of this topic. That could explain what you wrote about the statement not being updated.