Green up all selections rule did not trigger

[goat68]

I just noticed my bot on Newc 12:40, did not fire its greenup all selections rule which is supposed to trigger from -30seconds. Luckily I saw and greened it myself in play. Has anyone seen this happen before? It's a bit worrying as it exposes a potential large liability.

[Dallas]

The only reason for a rule not to trigger (assuming it triggers all other times and is set up correctly) is if the market wasn't refreshed.
viewtopic.php?f=37&t=11491

Also did you check the log to see if it triggered but just wasn't matched?

[goat68]

The only reason for a rule not to trigger (assuming it triggers all other times and is set up correctly) is if the market wasn't refreshed.
viewtopic.php?f=37&t=11491

Also did you check the log to see if it triggered but just wasn't matched?

I checked log, and it did not trigger.
I have guardian refresh at 100ms, and use restricted refresh, so only 2 markets were active.
Also streaming api enabled.

[goat68]

Automation log tab shows:
Green up | Triggers => 0/3
Last triggered: <empty>

[goat68]

I worked fine on Ling 11:50

Rule is Green All Selections
No conditions
Triggered at 30seconds before event start
until 10 seconds after
3 times, 2 seconds before rearm

[goat68]

Ok, maybe this is a clue, I also have an Export PnL rule that triggers at -15seconds till 0, and that did trigger but at 12:47 according to the log, 7mins late!!?

[goat68]

Could it have been an internet/wifi loss, would that show these symptoms? Rule triggering 7mins late...?

[Dallas]

Ok, maybe this is a clue, I also have an Export PnL rule that triggers at -15seconds till 0, and that did trigger but at 12:47 according to the log, 7mins late!!?

Can you post some screenshots of your full Guardian page, one with the log tab selected in the lower window and one of the automation tab selected (with a market selected after the rules have triggered).

[goat68]

Sure:

[goat68]

Ok, maybe this is a clue, I also have an Export PnL rule that triggers at -15seconds till 0, and that did trigger but at 12:47 according to the log, 7mins late!!?

Can you post some screenshots of your full Guardian page, one with the log tab selected in the lower window and one of the automation tab selected (with a market selected after the rules have triggered).

Certainly a bit weird, can connection issues cause this?

[goat68]

If the PC had lost network connection, would it still show a trigger attempt in the log?

[Dallas]

Ok, maybe this is a clue, I also have an Export PnL rule that triggers at -15seconds till 0, and that did trigger but at 12:47 according to the log, 7mins late!!?

Can you post some screenshots of your full Guardian page, one with the log tab selected in the lower window and one of the automation tab selected (with a market selected after the rules have triggered).

Certainly a bit weird, can connection issues cause this?

Yes, any connection or BF issues can cause a rule not to trigger.

I'm thinking it could be the later, there's another user posting on another thread at their bot never trigger, it was on the same same although it was IP there could still have been intermittent issues with BF - especially if its triggered fine the rest of the time like there's has done

[goat68]

Can you post some screenshots of your full Guardian page, one with the log tab selected in the lower window and one of the automation tab selected (with a market selected after the rules have triggered).

Certainly a bit weird, can connection issues cause this?

Yes, any connection or BF issues can cause a rule not to trigger.

I'm thinking it could be the later, there's another user posting on another thread at their bot never trigger, it was on the same same although it was IP there could still have been intermittent issues with BF - especially if its triggered fine the rest of the time like there's has done

Yes, it's triggered fine on all other races today.
Does BA have any error logs it records problems to?

[Dallas]

Certainly a bit weird, can connection issues cause this?

Yes, any connection or BF issues can cause a rule not to trigger.

I'm thinking it could be the later, there's another user posting on another thread at their bot never trigger, it was on the same same although it was IP there could still have been intermittent issues with BF - especially if its triggered fine the rest of the time like there's has done

Yes, it's triggered fine on all other races today.
Does BA have any error logs it records problems to?

If orders are rejected by Betfair or timed out these will be written to the log, but if there's a any type of loss in communications it can't report that (as there's no connection).

[goat68]

Yes, any connection or BF issues can cause a rule not to trigger.

I'm thinking it could be the later, there's another user posting on another thread at their bot never trigger, it was on the same same although it was IP there could still have been intermittent issues with BF - especially if its triggered fine the rest of the time like there's has done

Yes, it's triggered fine on all other races today.
Does BA have any error logs it records problems to?

If orders are rejected by Betfair or timed out these will be written to the log, but if there's a any type of loss in communications it can't report that (as there's no connection).

Doesn't Guardian trigger based on PC clock time, hence it could log rule failed to trigger due to comms error...?