Stop Loss problem against Lay

[Magic Murf]

Possibly I'm misundertanding the syntax of this trigger.

I layed a selection in a race from Excel.
Since I wanted to salvage some of my stake if the selection looked as if it was about to win, I used the trigger LAY-SLF1.10-L.
I expected this to do nothing unless my selection hit 1.10, in which case it should calculate and place a levelling back bet.

What actually happened was that my selection happily lengthened and looked rubbish .
Unfortunately a Stop Loss fired at about 100, just prior to the end of the race, so I lost pretty much my full liability despite my selection losing the race. [ouch].
I was watching the odds at the time, and at no time did anything resembling 1.10 appear ...

Any ideas as to what I've done wrong ??

[GaryRussell]

I've just tested that trigger and it will definitely only fire if the best lay odds are 1.1 or below. Can you look in your settled bet history on Betfair's website and check what the requested odds of the stop loss bet were. Also if you have a problem like like this in future it might be helpful to look in the transaction log under the account menu and check what it says about the stop loss being triggered.

[Magic Murf]

Hi Gary.

Sorry, should have included that info in my original post:

The "odds requested" in my bet history on betfair show as 100.77 (i.e. what the stake was matched at, which isn't helpful).
The transaction log entry in BA showed it as a Stop Loss requesting odds of 1.01 (which I assumed was just your standard code, to match at the highest available): I didn't see any detail of what the software had spotted to trigger the stop loss.

Unfortunately on betfair at the moment they're having a glitch regarding posting the IPMAX and IPMIN values for recent races, otherwise I'd have checked to see what the Minimum in-play matched transaction was for the race (just in case). But as I said, I was watching the race onscreen and didn't see any sudden downwards lunge of odds at the point when the stop loss fired.

Presumably the stop loss works off matched bets: if so, is there any history of betfair perhaps supplying suspect or unreliable data in this area?
Over the last two months I've had a couple of weird instances of stop losses firing for apparently no reason, but up until now I'd put it down to my mis-use of the trigger .

[GaryRussell]

Do you have "Fill missing prices" ticked in preferences under "Grid interface"? If there are no backers at any point then this option will put 1.01 in the lay odds column on the grid interface. I think this may have triggered the stop loss, although it's not what I intended. I am investigating if this is possible.

If you are using "Fill missing prices" then I would advise you untick it for the time being.

[Magic Murf]

'Fraid not, no.

Have never used Fill Missing Prices, so it's probably not the culprit.

[GaryRussell]

It was worse than I thought. In all cases where there are no backers it fires the stop loss. I am certain this is what happened in your case as the transaction log showed it requests odds of 1.01. I have fixed this bug in the pre-release version (1.1.0.63) which I will be making the official release shortly. You can download it using the link below.

http://www.gruss-software.co.uk/Betting ... _Beta1.msi

Sorry for the inconvenience.

[Magic Murf]

Double-ouch!

But great that it's fixed now.
I'd guess that also explains the previous occasions where I noticed similar behaviour.

Thanks for your weekend work!

I'm afraid I have another query about triggered Stop Loss (I just started playing with Stop Losses through Excel triggers).
If I place a bet through Excel with an Offset and a Stop Loss, using code along the lines of "BACK-TLF6.6-SLF120-L", the unmatched Lay bet at 6.60 doesn't seem to be deleted when/if the Stop Loss fires. So I can end up with both the Offset and the Stop Loss lays sitting waiting to be matched. And, potentially, get matches against both.

Is that functioning according to spec?
And, if so, is there some way I can set it to delete the Offset?
And should I kick this off as a new thread?

[GaryRussell]

You got me again. I must apologise I really thought this was all working correctly. The TLF6.6 part of the trigger was not being interpreted correctly.

I have fixed the problem. Please uninstall and re-install from the link I provided previously.