Alert if Fav loses first set

[FrankArch]

I have combined a few rules from the forum to get scores on ladder and watch list along with server and alert if fav loses. The problem is the alert on fav loses is consistently reversed. i.e. says Fav has lost first set when he/shes actually won ( last 10 alerts have been the same). I've obviously created some kind of conflict within the rules and would be grateful if someone has the time to point me in the right direction. Hopefully I have attached enough information.

[FrankArch]

one more

[FrankArch]

By way of update, the most most recent alert fired correctly. So appears to be random.

[FrankArch]

another example Rotti v Burruchaga with screenshot showing the save order file firing.

[Dallas]

There's nothing that can really conflict with that rule

I can see the fix order rule is triggering
So providing the alert rule is applied 'By Position (in order of favouritism 1'
It should work

Have you checked your main automation settings are to ensure the favouritism order is sorted by 'back price' ?
https://www.betangel.com/user-guide/bas ... tings.html

[FrankArch]

Appreciate the reply and yes auto settings appear to mirror those in the example.

[Dallas]

Appreciate the reply and yes auto settings appear to mirror those in the example.

What about the two SP stored value rules that trigger a few seconds before the Fix Order?
If those are written to the log and are capturing the price you could check that to see if the betting order is as expected

Or better still on the Fix Order rule use the Stored value tab and store the back price for each player, that way when it triggers you'll have a log of what there prices where when the order gets fixed

[FrankArch]

Appreciate the reply and yes auto settings appear to mirror those in the example.

What about the two SP stored value rules that trigger a few seconds before the Fix Order?
If those are written to the log and are capturing the price you could check that to see if the betting order is as expected

Or better still on the Fix Order rule use the Stored value tab and store the back price for each player, that way when it triggers you'll have a log of what there prices where when the order gets fixed

I've added both and will report back

[Dallas]

Appreciate the reply and yes auto settings appear to mirror those in the example.

What about the two SP stored value rules that trigger a few seconds before the Fix Order?
If those are written to the log and are capturing the price you could check that to see if the betting order is as expected

Or better still on the Fix Order rule use the Stored value tab and store the back price for each player, that way when it triggers you'll have a log of what there prices where when the order gets fixed

I've added both and will report back

And also just double check the Alert rule is applied 'by order of favouritism'
and it hasn't accidentally been changed to a Betfair row number

[FrankArch]

What about the two SP stored value rules that trigger a few seconds before the Fix Order?
If those are written to the log and are capturing the price you could check that to see if the betting order is as expected

Or better still on the Fix Order rule use the Stored value tab and store the back price for each player, that way when it triggers you'll have a log of what there prices where when the order gets fixed

I've added both and will report back

And also just double check the Alert rule is applied 'by order of favouritism'
and it hasn't accidentally been changed to a Betfair row number

Checked and ok

[FrankArch]

I've added both and will report back

And also just double check the Alert rule is applied 'by order of favouritism'
and it hasn't accidentally been changed to a Betfair row number

Checked and ok

Hi Dallas,

Please see attached. SP rule stored value last fired at 10.05.53 and shows player 1 at 2.44 and player 2 at 1.62 which is displayed in my sp on the ladder and is in line with Bet 365 pre match odds. However the stored value for the fix oder rule fired only 27 secs later and has wildly different values? (I notice the market was suspeded, but surely that wouldnt explain all the other times it's wrong.) should I just change the timings on the fix order rule to mirror those of the SP rule? I know you're a busy man and appreciate the time you're taking to look at this.

[Dallas]

And also just double check the Alert rule is applied 'by order of favouritism'
and it hasn't accidentally been changed to a Betfair row number

Checked and ok

Hi Dallas,

Please see attached. SP rule stored value last fired at 10.05.53 and shows player 1 at 2.44 and player 2 at 1.62 which is displayed in my sp on the ladder and is in line with Bet 365 pre match odds. However the stored value for the fix oder rule fired only 27 secs later and has wildly different values? (I notice the market was suspeded, but surely that wouldnt explain all the other times it's wrong.) should I just change the timings on the fix order rule to mirror those of the SP rule? I know you're a busy man and appreciate the time you're taking to look at this.

I never noticed it in your screenshot before but the fix order rule is triggering when the market turns in-play at the time all the unkept money briefly disappears, so it would be a lottery as to which one has the lowest back price and is deemed the fav for those first few seconds

In your log it shows both had the same back price of 1.1, and in cases of the prices being the same it will default the fav to the player in row 1

So to resolve this just set the Fix order rule to trigger pre-off,
You could arm once around the official start time time
Or set it to trigger multiple times re-arming every 60secs or so, and by adding a in-play condition to test the market is NOT in-play you'll know you have fixed the order sometime in the last 60secs before the match started

[FrankArch]

Checked and ok

Hi Dallas,

Please see attached. SP rule stored value last fired at 10.05.53 and shows player 1 at 2.44 and player 2 at 1.62 which is displayed in my sp on the ladder and is in line with Bet 365 pre match odds. However the stored value for the fix oder rule fired only 27 secs later and has wildly different values? (I notice the market was suspeded, but surely that wouldnt explain all the other times it's wrong.) should I just change the timings on the fix order rule to mirror those of the SP rule? I know you're a busy man and appreciate the time you're taking to look at this.

I never noticed it in your screenshot before but the fix order rule is triggering when the market turns in-play at the time all the unkept money briefly disappears, so it would be a lottery as to which one has the lowest back price and is deemed the fav for those first few seconds

In your log it shows both had the same back price of 1.1, and in cases of the prices being the same it will default the fav to the player in row 1

So to resolve this just set the Fix order rule to trigger pre-off,
You could arm once around the official start time time
Or set it to trigger multiple times re-arming every 60secs or so, and by adding a in-play condition to test the market is NOT in-play you'll know you have fixed the order sometime in the last 60secs before the match started

Great thanks

[Dallas]

Hi Dallas,

Please see attached. SP rule stored value last fired at 10.05.53 and shows player 1 at 2.44 and player 2 at 1.62 which is displayed in my sp on the ladder and is in line with Bet 365 pre match odds. However the stored value for the fix oder rule fired only 27 secs later and has wildly different values? (I notice the market was suspeded, but surely that wouldnt explain all the other times it's wrong.) should I just change the timings on the fix order rule to mirror those of the SP rule? I know you're a busy man and appreciate the time you're taking to look at this.

I never noticed it in your screenshot before but the fix order rule is triggering when the market turns in-play at the time all the unkept money briefly disappears, so it would be a lottery as to which one has the lowest back price and is deemed the fav for those first few seconds

In your log it shows both had the same back price of 1.1, and in cases of the prices being the same it will default the fav to the player in row 1

So to resolve this just set the Fix order rule to trigger pre-off,
You could arm once around the official start time time
Or set it to trigger multiple times re-arming every 60secs or so, and by adding a in-play condition to test the market is NOT in-play you'll know you have fixed the order sometime in the last 60secs before the match started

Great thanks

Any further problems just post back

[FrankArch]

I never noticed it in your screenshot before but the fix order rule is triggering when the market turns in-play at the time all the unkept money briefly disappears, so it would be a lottery as to which one has the lowest back price and is deemed the fav for those first few seconds

In your log it shows both had the same back price of 1.1, and in cases of the prices being the same it will default the fav to the player in row 1

So to resolve this just set the Fix order rule to trigger pre-off,
You could arm once around the official start time time
Or set it to trigger multiple times re-arming every 60secs or so, and by adding a in-play condition to test the market is NOT in-play you'll know you have fixed the order sometime in the last 60secs before the match started

Great thanks

Any further problems just post back

All working fine now. Thankyou.