My automation is not following the rules!

[fingers21]

I have a very simple automation rule set to trigger when a runner trades below 2.0 odds and lay the runner.

The problem is that it waits for for any selection to trade below 2.0 but then starts firing lay bets on anything with a heartbeat regardless of the odds and I can't figure out why.

The rule is set up to trigger on ANY SELECTION in-play where the best lay odds of the selection are less than 2.0. So I cannot figure out why lay bets at odds of 200, 220, 260 etc are placed regardless of the instructions.

I have even gone as far as setting individual rules for each runner i.e place a lay bet on selection in row 2 (Betfair order) if the best lay odds for the selection are less than 2.0 but I am still getting the same problem after the first lay bet triggers.

Anyone has come across such a thing before?

TIA

[jamesedwards]

Post your rulefile here and someone will find the issue for you.

[fingers21]

Here it goes

[jamesedwards]

What markets are you using these on?

Is this definitely the only rule you have running? (check 'automation rules' columns 2, 3, 4, 5).

[eatyourgreens]

hi,
from my limited knowledge i think your problem is because you are laying "any" when "any" is =< 2. therefore, when any is =< 2, your lay bet rule will fire on the first that meets your other conditions, then, when hit retriggers, if any is still =< 2, it will fire on the next one that meets the conditions.

try changing any to every, and add the condition " fixed odds =<2, on selection current from every"
you could also add "place bet trigger condition" <1 if you only want one lay per selection =< 2

hope im right, and not misleading you!
good luck

[fingers21]

I am running this in horse racing and I am not running any other rules. I even re-started bet angel just in case but still the same.

I will amend the rule as eatyourgreens suggested to see if it makes any difference.

[jamesedwards]

I am running this in horse racing and I am not running any other rules. I even re-started bet angel just in case but still the same.

I will amend the rule as eatyourgreens suggested to see if it makes any difference.

Perhaps there is a clue to the problem in your logs. Copy and paste the log from an affected race here. Might spot something.

[jamesedwards]

I'm not sure why this would make any difference, but try using a direct fixed odds condition rather than a stored value condition, as you are not using stored values.

z158.jpg

[Dallas]

I'm not sure why this would make any difference, but try using a direct fixed odds condition rather than a stored value condition, as you are not using stored values.

z158.jpg

You just beat me to that, I'm not sure if 'an entered' amount can be tested against a price
So what you've said could be right

Also this won't make a difference to it working or not but just to make it a bit cleaner if only testing for a price less than 2 you could just apply the rule to the fav rather than 'ANY'

[jamesedwards]

I'm not sure why this would make any difference, but try using a direct fixed odds condition rather than a stored value condition, as you are not using stored values.

z158.jpg

You just beat me to that, I'm not sure if 'an entered' amount can be tested against a price
So what you've said could be right

Also this won't make a difference to it working or not but just to make it a bit cleaner if only testing for a price less than 2 you could just apply the rule to the fav rather than 'ANY'

I've just tested the OP's rule and it works fine.

It must be something in his settings but for the life of me I can't think what might be causing it.

[Dallas]

I'm not sure why this would make any difference, but try using a direct fixed odds condition rather than a stored value condition, as you are not using stored values.

z158.jpg

You just beat me to that, I'm not sure if 'an entered' amount can be tested against a price
So what you've said could be right

Also this won't make a difference to it working or not but just to make it a bit cleaner if only testing for a price less than 2 you could just apply the rule to the fav rather than 'ANY'

I've just tested the OP's rule and it works fine.

It must be something in his settings but for the life of me I can't think what might be causing it.

Probably the Bet Confirmation message
The window could be behind his screen if he has it pinned

Or restricted refresh in Guardian is enabled

[fingers21]

Thanks for your replies guys. I followed eatyourgreens suggestion and the automation works fine now.