Greening up in play

[Blackmoor]

Dallas / All,

I encountered an issue earlier where an in play green up fired twice, resulting in a net lay, and a nasty and unnecessary loss.

Clearly the first green up lay didn't get matched, but my understanding was that when a green up is fired, any unmatched bets on the selection are cancelled, is that not the case ?? - I note that you generally have your config of retries set to 3, 5 sec re-arm in your examples, so assumed it must work this way, and that is what I have witnessed previously.

Initially I was expecting this to be are re-arm / in play delay issue, but the two lays are 39 secs apart, which would rule that out.

21/05/2017 14:40:53: Guardian has detected that the market is suspended
21/05/2017 14:40:54: Guardian has detected that the market is in-play
21/05/2017 14:40:54: Guardian has detected that the market is now unsuspended
21/05/2017 14:41:04: [G_Auto] : Placed closure bet with greening on Texas Rock by Laying 22.07 at 14.5
21/05/2017 14:41:43: [G_Auto] : Placed closure bet with greening on Texas Rock by Laying 10.74 at 25
21/05/2017 14:42:22: Guardian has detected that the market is suspended

This took the gloss off an otherwise decent day...

Any thoughts or insight would be very much appreciated.

Cheers

Steve

[Dallas]

I use at least 3 secs for the re-arm times to take account of the in-play bet delay so by doing the same their is no obvious reason why 2 bets should of been matched this far apart.

Have a check of your matched bets and using the Bet Id's check the times they were actually matched against the times they were placed from your log.
Are you using streaming or polling? also are you using the latest V1.48 Beta and if so have you changed any of the new greening options in the settings area?
It's now possible to instruct BA to cancel or not to cancel unmatched bets each time you green up with automation so its also worth double checking this to ensure this has not been changed.

[Blackmoor]

Thanks for replying Dallas.

The Id's and times match with the log, and were place 39 secs apart. I'm using streaming, with a 20 sec refresh, and refresh refresh set to [180,600]. It's clear the second green up was placed, which didn't cancel the first unmatched, and so two lays were fired in, and subsequently matched.

Clearly the default behaviour should be to cancel on greening, else you wouldn't provide templates/samples which have a multiple re-arm, as I cannot see how you could safely green up otherwise - especially in play.

I've been using 1.47 for some while, and had baulked from upgrading to a beta version, and I had issues with a previous version, and after a lengthy support call, was sent patches to fix bugs. For what I do, 1.47 had been working just fine - until today that is!

To be fair, I'm an extensive Guardian user, and have 100+ bots (many based on your library samples), however I have noticed odd issues on the past couple of releases. I've been charitable though, and being a Bet Angel fan, have put the issues down to odd behaviour/edge cases and maybe even Betfair behaviour, or my own logic, but today placing a simple £10 DOB, which resulted in a loss of ~£250 (when I actually should have actually have won) is so fundamentally awful, that I have completely lost faith in the product, and no longer have confidence in it. Given I rarely trade manually, I only really use Bet Angel for Guardian, and so am not sure where that leaves me with the product now.

Your input into this area of the product has been absolutely brilliant, and I have made good money by tweaking some of your templates, but I have to trust the underlying software, and that trust has now gone.

Steve

[Dallas]

I've just sent you a PM