Guardian bet error?

[rain91]

Hi,

its a guardian error oder user error?

My BACK bet conditions: "beragadas < 0.4"

I see in log, this value is 0.49 (0.49 - 0). After this the BACK bet goes out. Why?

Képkivágás.PNG

Képkivágás2.PNG

[Dallas]

Was there any stored values of the same name prior to the one you've highlighted?

[rain91]

Was there any stored values of the same name prior to the one you've highlighted?

This SV triggered unlimited, always armed for every selections, rearmed for every refresh. This SV watch the matched bets amount on every selection. It went with this value (0.49) a few minutes ago.

[Dallas]

Was there any stored values of the same name prior to the one you've highlighted?

This SV triggered unlimited, always armed for every selections, rearmed for every refresh. This SV watch the matched bets amount on every selection. It went with this value (0.49) a few minutes ago.

What was the previous values over say the last second or 2?

If it was an in-running bet there will be a delay to the matched bet, even in a pre-off market its going to take a fraction of a second to reach Betfair, get matched then the information sent back from Betfair to Bet Angel to be logged.

The log is only repainted every second so if that value is being set every refresh the bet will have been triggered from an earlier value

[rain91]

it was at 14:24:16 with value 0, and the following in the same second but after this 0.49 and in the same second 3 more with 0.49.

I think, the back bet condition watched the first, with value 0?

[Dallas]

it was at 14:24:16 with value 0, and the following in the same second but after this 0.49 and in the same second 3 more with 0.49.

I think, the back bet condition watched the first, with value 0?

Yes that's what it could have as it would of taken the first one if multiple values are stored within a second (as stored values are set locally there os no waiting for anything to go to and from BF)
Unless there was one set even earlier in which case that would have been used

[rain91]

unfortunately it happened again.
At 21:54:57 was the bet matched (I only know this from the fact that the value of sv changed in the log) and after this in the same sec the second back bet placed, but the value of sv prohibits it.
How can I prevent this?

In excel it was not problem. I cleared the status cell (PLACED) when the value of matched changed. Do you have any suggestions to avoid double bet?

[rain91]

I came up with a possible solution, but unfortunately it doesn't work either, the second back bet goes out, but why?
so the bottom line is: only place a back bet if the value of the matched back bet has changed

Conditions BACK
"totalamountbackmatched" not equal total matched back amount

Store a value by my BACK bet:
"totalamountbackmatched" = total matched back amount

CANCEL Back bet:
"totalamountbackmatched" = 99


Store a value only (1 times)
"totalamountbackmatched" = 99 (this is the start value)

So the "totalamountbackmatched" is an SV.

[Dallas]

How fast is your back bet rule re-arming?

If you are only wanting to place a single bet on a selection (when your conditions are met)
You could add a 'Number of place bet triggers condition' is equal to 0

Like Stored values that set locally so will prevent a the rule triggering a second bet on the same selection

[rain91]

Back bet rearming is 10 sec.

I want more back bets. I also have a cancel bet command, which is why it is also important that the trigger be unlimited (and come now LAY bets, if its hedged, can come the next back bet)
Therefore, unfortunately, 1 trigger is not an option for me


why is my previous example not working? in principle, this already watch the matched bet. If the matched bet (from betfair) changed, the condition can only be true after that.