I have a "Cancel All" rule that fires a certain number of seconds in play. However, rather than cancelling all at once it takes longer to cancel bets that were set with a "Fill or Kill" and seems to cancel them one or two per second after the rule fired.
Log has the "Fill or Kill" bets being described as "Killed" rather than "Cancelled" but they're not being killed by anything other than the "Cancel All" rule.
( I have the fill or kill time set at 20,000 secs so that's not cancelling them, they were placed shortly before start time )
How can I get everything to cancel in one hit please ?
The log shows for a race with only 6 runners with the last command to cancel taking 7 seconds after the initial. With larger fields and more bets unmatched it can take 20 or more seconds to cancel all which destroys the strategy I'm working on.
"Cancel All" has unwanted delay
Where are you connecting from?
All kill requests have to go through a queuing system if you're based in the UK you should be able to cancel several at a time with no noticeable delays, however, if you're further away like Australia then the added latency can cause issues when trying to kill so many at once, and the more your trying to cancel then longer the delay can be to those at the end.
If your backing/laying all then you could try using the rule type 'Cancel all unmatched bets (price dependant) to cancel those still unmatched at price point.
You can set a signal on the back/lay all rule
Then add a signal changed condition on the cancel all unmatched bets rule to set the time delay.
All kill requests have to go through a queuing system if you're based in the UK you should be able to cancel several at a time with no noticeable delays, however, if you're further away like Australia then the added latency can cause issues when trying to kill so many at once, and the more your trying to cancel then longer the delay can be to those at the end.
If your backing/laying all then you could try using the rule type 'Cancel all unmatched bets (price dependant) to cancel those still unmatched at price point.
You can set a signal on the back/lay all rule
Then add a signal changed condition on the cancel all unmatched bets rule to set the time delay.
I'm in Australia thanks Dallas.
I'm trying to cancel all which can be as many as 4 fill or kill bets per runner. Less if some have already been matched. But yes that's a lot if they don't all cancel in one action.
So if I understand you, it's my straight back bets (not fill/kill) that cancel in one hit but anything with a fill or kill will be done step by step.
I'm unsure what you mean with the price dependent solution suggested.
Note that my bets are not backing all at same price, they are backing at set % above and some at ticks above each runners price just before the race start. Then offsetting at % or ticks below back price. Does that mean "Cancel all unmatched bets (price dependant)" is still a viable solution ?
I'm trying to cancel all which can be as many as 4 fill or kill bets per runner. Less if some have already been matched. But yes that's a lot if they don't all cancel in one action.
So if I understand you, it's my straight back bets (not fill/kill) that cancel in one hit but anything with a fill or kill will be done step by step.
I'm unsure what you mean with the price dependent solution suggested.
Note that my bets are not backing all at same price, they are backing at set % above and some at ticks above each runners price just before the race start. Then offsetting at % or ticks below back price. Does that mean "Cancel all unmatched bets (price dependant)" is still a viable solution ?
The price dependant would only really have worked for you if you were using back/lay all selections and therefore knew the fixed price.
Unfortunately the way your placing the bets and due to your location there isn't a simple solution to having them killed unless you were to use a VPS here in the UK as that would have less latency to Betfair's server
Even then if you're placing up to 4 per runner and its a 15-20 runner field that 60-80 bets to kill
I've tried it with as many as 20 and can kill them without delay from here in the UK but expect you may still run into some delays with that amount.
Unfortunately the way your placing the bets and due to your location there isn't a simple solution to having them killed unless you were to use a VPS here in the UK as that would have less latency to Betfair's server
Even then if you're placing up to 4 per runner and its a 15-20 runner field that 60-80 bets to kill
I've tried it with as many as 20 and can kill them without delay from here in the UK but expect you may still run into some delays with that amount.
Hi,
I'm in the UK and use the Cancel All Unmatched bets function in play after a time lapse. I only have one bet per horse.
If there are 14 or more bets to cancel, the log will show two entries. Most will be cancelled at the specified time and the rest a second later. This applies to the UK and Australia.
I'm in the UK and use the Cancel All Unmatched bets function in play after a time lapse. I only have one bet per horse.
If there are 14 or more bets to cancel, the log will show two entries. Most will be cancelled at the specified time and the rest a second later. This applies to the UK and Australia.