Why does my trigger choose the wrong horses here?

Hi, I've noticed since I started playing with triggers that the trigger seems to get confused (or more likely it is me) when it is checking my conditions.

In the below example it has chosen two horses as the two faves (#1 and 6) who are paying around 14 and 24 respectively, when the two faves are paying around 3 and 4. How is my trigger wrong?

NOTE horses #1 and #6 are definitely not the favourites. The faves are # 2 and #4. Also the faves price IS greater than 2, just that the trigger has selected the wrong horse... NOTE that a split second after this it changes the two selections. Please believe me, the market did not change much in that few seconds.

Checking market "Horse Racing / AUS / WFrm (AUS) 15th Jul / 14:30 R4 2200m Hcap".
14:35:12   Checking condition and Selection's Rank is equal or less than 2.
14:35:12   Condition is: TRUE. valid for 2 selections: 1. Lucky Liaison, 6. Gamblers Blues.
14:35:12   Checking condition and Favourite's Back Price is equal or greater than 2.
14:35:12   Condition is: FALSE.
14:35:12   Remaining conditions in the block will not be checked.

Then it changes to this (note the time)
14:35:17   Condition is: TRUE. valid for 2 selections: 1. Lucky Liaison, 2. Ashkannd.

TRIGGER:
 For ALL MATCHING SELECTIONS IN IDLE OR SUSPENDED
Selections rank is equal or less than 2.
Favourites back price is greater than 2
2nd favourites back price is less than 5
3rd favourites back price is greater than 13
Selections trigger expression match_b_book is equal or less than 80.

Here is a link to the bookies starting prices if it helps
https://www.tab.com.au/racing/2015-07-15/WARWICK-FARM/WFM/R/4

The bookie SP.s are of no help as they will be diferent from BF live prices.   If you want to bet according to the values of Betfair SP, then you can only do this in running by using the variable actual_sp.  Unfortunately, you will only be able to bet at live exchange prices which may be widely different from BSP and this will be a particular problem in Aus racing with its low liquidity.

Please remember that the conditions are checked on every refresh, so the horses selected could change very easily without you noticing it.  Again the low  liquidity in Aus racing will exacerbate this.

OK, bookies prices are quoted just as a point of reference. Trust me when I say that one minute from the off at Warwick Farm, a $24 chance is never going to drop to $5.

Luckily we have Time Machine.

I am attaching the screenshot of this race at the moment when Lucky Liaison and Gambler's Blues were the top two favourites.

It is perfectly feasible for the favourites to change over a couple of refreshes, especially towards the end of the event.

Hi,


Well that a was a bit of time wasted on my behalf. I thought the trigger was set to IDLE or SUSPENDED and went through my TM database trying to recreate the scenario. It was a messy race, and the low liquidity on the market clearly caused prices to drop.

Anyway I hope there was no real harm done to your bank DG. And if look at the attached link to the recording of the race you can see is why it bounced around so much.

Thanks guys, that time machine screenshot was ""in play"".
Larp, my settings are set to idle or suspended. I assumed it would stop logging after the jump. I guess I assumed it was still an idle market.
Can you confirm that even tho settings are at idle or supended, MF will still log but will NOT place a bet?
See attached file, just a screenshot showing settings at idle or susp.
I am only in test mode with triggers but I know that unless I trust them fully I will never use them in real mode...

Any way I can stop MF logging after the jump? It creates a lot more data to scroll thru.

You can just stop refreshing markets after the off if you don't plan on betting in them then.