Fill or Kill Bet Anomally

[Monsoon4187]

I set a back bet with offset and stop and to prevent the offset lay bet being placed if the back bet was not matched. This is what happened (extract from log):-

07/03/2020 16:57:17: £ 2.00 Back bet placed on Craiganboy at 1.21. Entirely unmatched when it initially reached the market.
07/03/2020 16:57:29: [G_Auto] : £ 2 unmatched bet (Ref:197495494824) was killed.

Problem is the back bet was matched with betfair, went on to lose and I lost my stake.

What is the point of the Fill or Kill bet if it fails to do what is says on the tin?
Anyone else experienced this? Is there a clitch or another condition that can be applied.

Thanks

[Bet Angel]

There have been occasions where the betfair API has failed to report correctly on a bet cancellation (the kill), but as far as we're aware we've worked around every one of those issues in the latest version of Bet Angel v1.54.1 - so check that you are using that version.

Even so, for years we've had routines to warn in the logs when such issues were detected and Bet Angel would go into a ten second bet detection routine to compare cancellation results with matched bet information. As there are none of those warnings in your log, I suspect that you also may not be refreshing the market in Guardian particularly quickly, so check the 'Last update' column in Guardian to see how frequently you are allowing the market to get price/bet updates and consider: changing the refresh interval, using exchange streaming, using restrict refresh and/or 'Automatically switch Bet Angel market'. All of those features can be used to increase the frequency of updates for a given market.

[Monsoon4187]

Hi

Thanks I do need to update my version currently running v 1.53.1, My refresh rate was set at 300ms.