I encountered another lapsed bet and another winner.
GB / Newt 10th Jun / 01:30 3m3f Hcap Hrd Little Eaglet Back 27629479215 11-Jun-13 01:29 C 5.9 46.01 Unmatched
Here's the mystery. I run UK races on the MFPro 6 platform. The loaded xml is named UKsys_02Jun_UKR (Named so, beause that;s the day I changed it after encountering the original problem from this thread). Within it, is a trigger that handles horses (matched from a list on Excel) that are between $2.0 and $9.0. The trigger is named 'UK Naps <=3 <$5_2' the log report seems to convert the operator to words, so the log file is named 'UK Naps UK Naps less than =3 greater than $5_2.txt' I note the range doesn't match the trigger, however I double checked and the price range is set to
Selections back price is between 2 and 9
Formerly, from an xml file I had a similar trigger that handled the same horses that were between $5 and $9. It had a price setting of r_ticks(back_price,2)
My problem is, I suspect, I have missed being matched and it's is because the bet was being submitted as r_ticks(back_price,2). So I changed the trigger to back_price2. To give me some insurance I will get matched.
Today after discovering I missed another $225 I went searching why. What I found is very unusual. Here's the extract from the MFPr6 log.
"Checking condition: and Selection's Back Unmatched is equal to 0
Condition is true. valid for 1 selections: Little Eaglet.
Checking condition: and Selection's Lay Unmatched is equal to 0
Condition is true. valid for 1 selections: Little Eaglet.
Checking condition: and Selection's Back Price is between 5 and 9
Condition is true. valid for 1 selections: Little Eaglet.
Going to Back in market "Horse Racing - Todays Card / 01:30 Newt 11 Jun" on the following selections :
Little Eaglet, $ 46.01 at 5.90"
The important section is this "Selection's Back Price is between 5 and 9" This is a condition from the old trigger?? A previous rule I changed after I had a similar issue that I posted on this thread. At least 01Jun13.
Now the trigger loaded doesn't have that rule. Its rule is
Selections back price is between 2 and 9
and the price submission was r_ticks(back_price,-1) I have since changed to to back_price2 today but I doubt it will make a difference while this xml keeps using this old rule from the Ethernet.
How and why is this trigger retaining an old rule from a trigger block I can't find? I recall this rule and I have checked old xml files? It is not in recent updates but I know the rule.
Note: I only have one MFPro running at night on this PC and on this account. I have another laptop running but different account. How/Why is this happening?