Automation Please Help

[MHoughton]

Please can somebody help with these two issues:

I have an automation set up to “place a lay bet between certain odds”, e.g: between 3 and 3.15 on guardian nominated selection 1. It is placed at 0 ticks above the best reverse market price. One condition is that the number of unmatched bets on the guardian nominated selection 1 is equal to 0.
I also have a rule to cancel unmatched bets on this selection if the odds drift by 1 tick. Rule type “cancel unmatched bets on selection (Price dependent)”. Price is 1 custom tick below the best reverse market price and the action is to cancel “lay bets only” less than or equal to price parameter.

Issue 1: It will place a lay bet of say £10 which is unmatched. At that point, unmatched lay bets are obviously not equal to 0, but for some reason, sometimes a few seconds later it will double up and put another lay bet in for £10, which then leaves me with 2 lots of £10 unmatched bets. I only want the next lay bet to be placed when the corresponding back bet has been matched. The back bet greens up straight away using a smaller stake, so I can’t use the monetary value of matched lay bets is equal to the monetary value of back bets.

Issue 2: If I put a lay bet in at odds of 3 and it is unmatched, then if the odds on the low side drift to 3.05 then I want the unmatched bet to be cancelled. This is not working at all and sometimes it will drift towards 4 and still not get cancelled until the fill or kill kicks in

[the4droogs]

For Issue 1 I'd suggest putting a wait time on your rule that triggers the bet. 5-10 seconds should be enough. It can take a little while before the bet is accepted and placed into the queue. So if your refresh rate is fast enough, the next time the rule is triggered the unmatched lay bets are still zero because the previous bet hasn't gone through yet, so the rule triggers and puts a second, third fourth bet until the first bet clears and the unmatched bet amount changes. Hope that makes sense.

For issue 2 it is unclear what is happening without more information. Most likely there is a logical error in your conditions. Here are some things you could check:

• You have the right selection in your cancellation rule

• Your cancellation rule is not price dependent (or if it is you have the right price)

• Your cancellation rule is set to fire multiple times and has the correct time constraints in place

• Your conditions are correct

One technique I use to debug complex conditions is to create a seperate rule that triggers for each of the conditions individually. Then if it fires, set a signal/stored value and log it. That way you can narrow down which condition is failing.