Issue with condition: Race Distance

[lotora]

This condition stops the rule from triggering, independent of whether the condition is met or not. I don't understand why.

[Dallas]

That will allow it to only trigger on races less of 1m3f or less

Since 23rd Dec only Wolverhampton races has had race distances fitting this criteria yesterday - and will again in this evening card

[lotora]

That will allow it to only trigger on races less of 1m3f or less

Since 23rd Dec only Wolverhampton races has had race distances fitting this criteria yesterday - and will again in this evening card

Thanks! Just had to find out if there was a technical issue with this condition.

[Dallas]

That will allow it to only trigger on races less of 1m3f or less

Since 23rd Dec only Wolverhampton races has had race distances fitting this criteria yesterday - and will again in this evening card

Thanks! Just had to find out if there was a technical issue with this condition.

There's no issues with any conditions, options or features of Bet Angel, whenever something new is added it goes through months of extensive testing during development, only once confident it works is it then released as a beta to the forum as this allows an even greater range of use to be tried and tested so anything now uncovered in development testing can be fixed before its finally released as an official version.

Any bugs uncovered at this stage will be those deeply buried and only be found by chance when using specific options and following a series of steps in a set order (as it's impossible to ever test everything possible to do with the software)
For example, a rule with a stored value set at Bet Angel level doing a calculation involving a range of Values in a history list may fail to perform the calculation correctly work when imported to an settings file that has options 'X, Y and Y' enabled while options 'A, B and C' are not in use and the refresh rate is below 'X'
Apart from those sorts of scenario's you can be sure everything works as it should