Guardian GreenAllSelections issue on re-try

User to User support only. For technical support visit www.betangel.com/support/
Post Reply
User avatar
goat68
Posts: 2019
Joined: Tue Jun 30, 2020 3:53 pm
Location: Hampshire, UK

Hi,
I'd like to raise a potential issue, or maybe "implementation" clarification on the following issue I saw on a market today.

I have a GreenAllSelections rule that triggers at -10seconds before the scheduled start, triggers 3 times, with a 5second re-arm.
What I saw today was that on one market my greenup was well out, traded selection was about -£1.70, other selections -£0.19, the reason being because the greenupallselections rule had double Layed the required greenup amount.

This is my Settled bet history for the market:
15:53:28 15:50 Beverley Qawamees - Win
Betfair Bet ID 1:230973218932 | Placed: 22-Apr-21 15:45:05 Lay 4.80 4.74 -- 18.01 4.74 Won
15:53:28 15:50 Beverley Qawamees - Win
Betfair Bet ID 1:230973613940 | Placed: 22-Apr-21 15:49:45 Back 4.40 5.42 -- -- -5.42 Lost
15:53:28 15:50 Beverley Qawamees - Win
Betfair Bet ID 1:230973627131 | Placed: 22-Apr-21 15:49:55 Lay 4.40 0.25 -- 0.85 0.25 Won
15:53:28 15:50 Beverley Qawamees - Win
Betfair Bet ID 1:230973634251 | Placed: 22-Apr-21 15:50:00 Lay 4.40 0.24 -- 0.82. 0.24 Won

This is from the automation log when the GreenAllSelections triggered:
22/04/2021 15:49:50: [G_Auto 1] : Greened up Qawamees by Laying 0.25 at 4.3
22/04/2021 15:49:55: [G_Auto 1] : Cancelling bets 230973621239
22/04/2021 15:49:55: [G_Auto 1] : Greened up Qawamees by Laying 0.25 at 4.4
22/04/2021 15:50:00: [G_Auto 1] : An error occurred while cancelling bets: The entire order has been rejected.
22/04/2021 15:50:00: [G_Auto 1] : Cancelling bets 230973627131
22/04/2021 15:50:00: [G_Auto 1] : Greened up Qawamees by Laying 0.24 at 4.5
22/04/2021 15:50:54: Guardian has detected that the market is suspended
22/04/2021 15:50:56: Guardian has detected that the market is in-play

As you can see on the 3rd trigger the Cancel failed, the most likely reason is because it matched in Betfair as can be seen for 230973627131 in the Settled Bet History, however guardian went on submitted the 3rd Greenup Lay order regardless.
1) should it have not queried the bet status after the failed Cancel?
2) is the actual order of events by the guardian execution thread as depicted by the message log for the 15:50:00 entries? The reason I ask as it shows the "An error occured msg", followed by the "Cancelling bets 230973627131" message, which is obviously the wrong way round? If that is the case does that then actually mean guardian placed the "Greened up Qawamees by Laying 0.24 at 4.5" order first, then issued the "Cancelling bets 230973627131", and then got the "An error..."?
In which case would it be more logical to attempt to Cancel the previous order first, before issuing the new Greenup order?

Thanks
User avatar
goat68
Posts: 2019
Joined: Tue Jun 30, 2020 3:53 pm
Location: Hampshire, UK

It's probably at least worth noting, even if the implementation logic is as expected, maybe the log message ordering should be corrected?
Post Reply

Return to “Support”