I have a condition on a rule that doesn't seem to be triggering and hoping someone can point me in the right direction.
My logs show them as having the same value;
1/07/2024 13:15:23: [G_Auto 1] : Store Value (Shared) for market: DB1ID = 61372083
1/07/2024 13:21:01: [G_Auto 5] : Store Value (Shared) for market: 1st_place_no = 61372083
I know this rule works but the moment I add this condition it doesn't trigger. What have I missed?
Rule condition not working as expected
What conditions do you have?Jolissa wrote: ↑Mon Jul 01, 2024 5:07 amI have a condition on a rule that doesn't seem to be triggering and hoping someone can point me in the right direction.
Capture.JPG
My logs show them as having the same value;
1/07/2024 13:15:23: [G_Auto 1] : Store Value (Shared) for market: DB1ID = 61372083
1/07/2024 13:21:01: [G_Auto 5] : Store Value (Shared) for market: 1st_place_no = 61372083
I know this rule works but the moment I add this condition it doesn't trigger. What have I missed?
- jamesedwards
- Posts: 3990
- Joined: Wed Nov 21, 2018 6:16 pm
Check there's not a mistake with the names or levels of the SVs.
Double checked names and stored values and they all look fine. I can only assume that the Bet ID is stored as a text field, not a number. (any way to check that?)
What I trying to do is create a condition that simply tests if a Stored Value (Market level) for a runner selected in a previous rule has won or lost. I thought it would be easy but I am hitting brick walls.
What I trying to do is create a condition that simply tests if a Stored Value (Market level) for a runner selected in a previous rule has won or lost. I thought it would be easy but I am hitting brick walls.
did you try this?Jolissa wrote: ↑Tue Jul 02, 2024 7:20 amDouble checked names and stored values and they all look fine. I can only assume that the Bet ID is stored as a text field, not a number. (any way to check that?)
What I trying to do is create a condition that simply tests if a Stored Value (Market level) for a runner selected in a previous rule has won or lost. I thought it would be easy but I am hitting brick walls.
"another thing to try might be to subtract one from the other and make sure it equals zero (in case there's a text v num issue or similar)"
Took me a while to work it out but I think I have confirmed they are stored as numbers and that has me looking for some other issue.
.
.
If I can add them into a stored value, thats means they are numbers doesn't it?
.
.
If I can add them into a stored value, thats means they are numbers doesn't it?
You do not have the required permissions to view the files attached to this post.
On the (general) automation tab, you have the option to (allow trigger when the market is suspended). You need to tick that if you want a file to trigger when the market is closed. Its in the trigger section.
I would also add a (market status condition) = closed, although I'm not sure that will make much difference.
I would also add a (market status condition) = closed, although I'm not sure that will make much difference.
You do not have the required permissions to view the files attached to this post.
Yep. Feel free to post more details. We'll get you there. It's not much fun spinning wheels for a week
Usually when this happens (when things should work by don't), you've missed something elsewhere in the logic.
The simple troubleshoot here is to duplicate the rule which doesn't work, and inverse the condition which fails.
In your case that's 'DB1ID' for mkt IS NOT equal to '1st_place_no' for mkt. And on that rule print stored values for the variables being checked to see which onr made the rule fail, and backtrack from there.
Looking at your posts, though, I'd guess you probably got it wrong when you say the reason it's not firing is because of the newly added condition. It's probably your rule type.
Solution: Your file will probably work as expected if you change the rules from firing on 'ANY' to 'EVERY'.
Currently you're checking one random runner to see if they've been settled as the winner (ANY = 1). You'd usually use ANY when you are checking only mkt level SV's. Anything selection-level (in this case it's 'result' aka win status for the selection), you want to have the rule apply to EVERY selection as anything not settled as a winner will be = "" and fail the rule (most selections in a place mkt) Make sure the rule which sets 'result' is set to EVERY, too.
Gl
The simple troubleshoot here is to duplicate the rule which doesn't work, and inverse the condition which fails.
In your case that's 'DB1ID' for mkt IS NOT equal to '1st_place_no' for mkt. And on that rule print stored values for the variables being checked to see which onr made the rule fail, and backtrack from there.
Looking at your posts, though, I'd guess you probably got it wrong when you say the reason it's not firing is because of the newly added condition. It's probably your rule type.
Solution: Your file will probably work as expected if you change the rules from firing on 'ANY' to 'EVERY'.
Currently you're checking one random runner to see if they've been settled as the winner (ANY = 1). You'd usually use ANY when you are checking only mkt level SV's. Anything selection-level (in this case it's 'result' aka win status for the selection), you want to have the rule apply to EVERY selection as anything not settled as a winner will be = "" and fail the rule (most selections in a place mkt) Make sure the rule which sets 'result' is set to EVERY, too.
Gl
Thanks everyone for your help here. Deleted the rule (painful) and rewrote from scratch, now working as intended, so very happy.
Doing final testing, but I now have a rule level P&L, so I can run multiple rules on a market (Dogs and Gallops) that can then deliver multiple bets and still manage the P&L of each of those rules individually.
I get the best results when I have simple stops on profits and losses at a rule level. This will save me hours and hours of staring at a screen all day.
Doing final testing, but I now have a rule level P&L, so I can run multiple rules on a market (Dogs and Gallops) that can then deliver multiple bets and still manage the P&L of each of those rules individually.
I get the best results when I have simple stops on profits and losses at a rule level. This will save me hours and hours of staring at a screen all day.