BF's in-play delay causes bets to be fired twice?

[weemac]

I'm getting the hang of Guardian, but am having a problem on football in play.

I want to place a back bet, subject to time and price stipulations, with the proviso that there's only one pre-existing matched £10 back bet, which was matched before kick off. So I use the condition "Back bets matched = £10", the plan being to now have £20 in 2 x £10 matched backs.

But the in-play bet is being fired twice, presumably because Guardian doesn't know that the first bet's on its way into the market, subject to BF's bet placement delay. It doesn't seem to matter what rearming delay I impose.

Can anyone suggest a way round this? I'm currently reducing the second bet to £5, knowing that it'll fire twice, but that seems far from ideal.

[Dallas]

Your using the correct condition so I cant understand why its firing twice for you and the re-arm should also stop this especially if its over 10 secs unless some other part is causing a conflict somewhere.

You could try adding the condition "number of placed Bets triggers condition" and set it to "selection" equal to 0

This will ignore your pre off bet if it was manually placed, if it was a auto bet set it to "selection" less than 2

[weemac]

Ah, I might have goofed up. I had a 3rd bet rule for later in the match, which I might have coded badly. It's possible that the 3rd bet fired earlier than it should have. Unfortunately I removed that rule earlier today, so I'll re-introduce it (properly) and re-test things.

I wasn't expecting practice mode to be so useful......it's highlighted loads of flaws in my rules.

Thanks for your speedy, helpful response, dallas.