entry back out of range

I set a very simple rule that comes in when the back odds is between 1.10 and 1.20 (using between) but it happens that I get into much higher odds, why?

Hi 

If you see logs you will find a reason for that.

Exemple the price may give a huge jump, between triggers firing and bet placement by betfair api
There are many other reasons.

Pcal

Code: [Select]

10:20:50 Going to BACK on 1 selections:

      Alejandro Tabilo, € 10.00 at 1.16;

Program logAccount statementTrigger logs


why?

how can i avoid? I would expect that the program does not like it because it is out of range

hi
as pcal72 said , Example the price may give a huge jump, between triggers firing and bet placement by betfair api.
the trigger sent the bet at 1.16 as it should have because the condition is when the back odds is between 1.10 and 1.20
BUT just before betfair received the bet the price jumped to 1.34 , so betfair gave you the best price available.
IF the price dropped to 1.10 the bet would have been unmatched at 1.16 .

I checked the movements of the odds ... in practice it was fixed at 1.26 and dropped a moment to 1.16 and then back up to 1.30. how can i avoid these false movements?

I weighed a check between the distances of the height ... 5 ticks

Backprice equal or greater r_ticks(lay_price, -5)

Or this

Yes both solutions are great to avoid this gaps