Laying pre-off £2 liabilty

[NorthView]

I'm getting apparently random failures to lay horses via Excel for a liability of £2.

The lay doesn't appear in Gruss or in the transaction log but the workaround lay at odds of 1.03 does.

Other lays are executed fine and I can't see any difference between the succesfuls and the failures.

The BA_Diagnostic-2023-02-18.log doesn't contain any clues.

[GaryRussell]

I will be releasing an update shortly and will include more information in the diagnostic log to catch this. Do you know what the specific odds and stake are for any of these bets?

[NorthView]

Thanks Gary.

Some of these are layed correctly, some aren't.

One from yesterday I had to lay again manually was at 7.4 for £0.31

All of today's were fine but the next day it happens I'll post the info from the transaction file.

[NorthView]

Two errors today: Premiumaccess and Tollerton Forest

:

Gruss1.jpg (253.75 KiB) Viewed 5110 times

[NorthView]

Just had a thought. I'm rolling through a list of races with refresh = 0.5 seconds and pausing at each for 3 refreshes in VBA before moving to the next.

Is this a factor?

[Captain Sensible]

The API errors in the above screenshot each occur with a liability of less than £2. Maybe you need to tweak your stake calculation

[NorthView]

Other lays less than £2 liability went through fine eg

Gruss2.jpg (14.18 KiB) Viewed 5079 times

[NorthView]

Raised the liability to £2.10 but still Noahs Abbey failed:

Gruss3.jpg (150.5 KiB) Viewed 5065 times

[Captain Sensible]

Is it gruss laying at these weird stakes of 0.128888 or your calculations? Could you not simply round () the stake before it's submitted see if that clears any failures.

[Captain Sensible]

Round to 2 decimals*

[NorthView]

Thanks CS. I'm rounding to 2 DP now and got two errors today:

Gruss4.jpg (293.64 KiB) Viewed 5038 times

This is through triggered betting in Excel. When I later go into Gruss to cancel the workaround lays and place the lays I want manually they always work correctly.

[GaryRussell]

I will release an update tomorrow. Hopefully this will reveal what's going on in the diagnostic log. In the meantime if you have time could you send today's diagnostic log to admin@gruss-software.co.uk. I know you said it does not contain any clues, but I might see something that isn't obvious.

[NorthView]

Thanks Gary. I've sent the diagnostic log.

[GaryRussell]

Just had a thought. I'm rolling through a list of races with refresh = 0.5 seconds and pausing at each for 3 refreshes in VBA before moving to the next.

Is this a factor?

Looks like it is the issue. The next market is starting to load before the minimum bet process is complete.

1) When you link to Excel do you have "Place bets in background ..." ticked? I recommend it is not ticked so that it won't move to next market until bet processing is complete.

2) Does the code that inserts "-1" into cell Q2 only execute after the prices refresh? ie. it would look something like the following. I always recommend using the trigger at this point to avoid any issues.

Code: Select all

Private Sub Worksheet_Change(ByVal Target As Range)
    If Target.Columns.Count = 16 Then
        If refreshCount = 3 Then
            Application.EnableEvents = False
            [Q2] = -1
            Application.EnableEvents = True
        End If
    End If
End Sub


[NorthView]

Right. I made both of those changes and today's lays went in perfectly. I'll continue to check but I think it's fixed now.

Cheers Gary.