I have a Football automation running which places bets on the "favourite" score at a certain time.
The rule fires just fine as the back bet is being placed at best market price at that precise time.
However...
I have had this running in test for a few big days of football and due to the larger number of 3pm matches covered, coupled with some faster odds movement due to goals - some back bets do not get matched as the odds drop within a second or so.
How can I deal with this? - as Id still like to place the bet as long as its the favourite.
Im thinking Fill or Kill? - which Ive tried, but the rule doesnt fire again. Theres is also risk that by the time the cycling passes again there is a new/different favourite.
Any thoughts welcome on how to deal with this scenario. Im looking to bet on the favourite at a certain time, and for the rule to persist in this, until this is achieved. But clearly avoid doubling up or betting on 2 different options.
Back Bet Odds Shift During Guardian Cycling
When you have more markets than usual in guardian you can try increasing your trigger arm time window, so if you had up to 60 markets and where using a 1 sec guardian refresh rate then have your back bet armed for at least 1 min and have it place at lower price ie, 2nd or 3rd best price just in case there is a odds movement during the bet placement delay