Urgent

[GaryRussell]

Is your actual question regarding why the following transactions are in the log at all? If so they have always been recorded It's just recording the transactions it needs to make to place a below minimum stake bet. It's so you can see if any of these transactions had a problem in case a bet does not appear to be submitted at all.

49 20/3/2011 14:19 14065523615 Below minimum stake, lay 2 @ odds 1.01 OK 1533
50 20/3/2011 14:19 14065523672 Below minimum stake, update stake from 2 to 2.82 NEW_BET_SUBMITTED_SUCCESSFULLY 1472
52 20/3/2011 14:19 14065523843 Below minimum stake, update stake from 2 to 2.49 NEW_BET_SUBMITTED_SUCCESSFULLY 1583
53 20/3/2011 14:19 14065523049 Below minimum stake, cancel lay of 2 @ odds 1.01 REMAINING_CANCELLED 586

[GaryRussell]

probably this is happening because a a small part of my back bet is getting matched..

i can't thing of another reason.

Yes, if the lay stake is smaller than the original back stake when using BACK-TL3 it must because it was a partial match. The diagnostic log will confirm this. The file is named BA_Diagnostic.txt and is located in "c:\temp\Betting Assistant Logs". You will find entries beginning "Placing offset bet" and in that entry you will see an unmatched stake amount which will confirm if you are getting partial matches.

[mak]

I will look at it later
I start looking at it because today i get a lot of spikes in the actual refresh history (chart) and really don't know why?

Can you tell me if possible how things are at your end (all spikes are i/r mainly at the last stages of the race)

Thanks