Always armed

[sibur]

I have a rule that is always armed. However it doesn't always seem to trigger after the market has closed. I do have the checkbox ticked "Allow trigger when market suspended". If this is by design what options would be best to use so the rule would trigger after market closure?

[jamesedwards]

I have a rule that is always armed. However it doesn't always seem to trigger after the market has closed. I do have the checkbox ticked "Allow trigger when market suspended". If this is by design what options would be best to use so the rule would trigger after market closure?

I think what happens is Guardian does one final sweep once it registers a market has closed and then stops. So you need to initiate everything in the correct order during that single final sweep.

[Dallas]

Do you have a 'Market Status' condition on the rule?
If not It maybe that the rule is triggering at an earlier time when the market suspends briefly ie, when turned in-play

[sibur]

Hi Dallas. I don't have a market status condition, no, but the rule never triggers and I can see that from the Automation tab next to log. I will add it in however and see if it makes a difference.

[sibur]

Actually the rule may or may not need to trigger when the market is closed, so I don't really want to add the market status condition because if at all possible I would like the rule to fire as soon as possible after the market is suspended. The condition it's currently triggering on is a market SV that is definitely set. This rule sometimes fires correctly. The rule is set to fire on any selection.

[sibur]

I have a rule that is always armed. However it doesn't always seem to trigger after the market has closed. I do have the checkbox ticked "Allow trigger when market suspended". If this is by design what options would be best to use so the rule would trigger after market closure?

I think what happens is Guardian does one final sweep once it registers a market has closed and then stops. So you need to initiate everything in the correct order during that single final sweep.

didn't see this. Need to have a think

[sibur]

Is there any docs about this final sweep. Never saw this before and may explain other issues in past

[sibur]

Will a rule trigger after market closure if you use the trigger option 'relative to market start time' and have a period well beyond when the event is due to end?

[jamesedwards]

Will a rule trigger after market closure if you use the trigger option 'relative to market start time' and have a period well beyond when the event is due to end?

I *think*, only if Guardian first registers the market as closed during your set period.

I work on the principle that when Guardian first arrives at a closed market; it registers the market is closed, completes a final sweep through your rule file, then doesn't revisit that market ever again.

[Dabbla]

You may want to nest 2 'Market Status' condition..
Is it (Suspended) or (closed).

[jamesedwards]

Will a rule trigger after market closure if you use the trigger option 'relative to market start time' and have a period well beyond when the event is due to end?

I *think*, only if Guardian first registers the market as closed during your set period.

I work on the principle that when Guardian first arrives at a closed market; it registers the market is closed, completes a final sweep through your rule file, then doesn't revisit that market ever again.

Although this response from the Bet Angel AI help would suggest my assumption is not correct.

z142.jpg

[sibur]

Yes well I'd hope that was the case and I think that's how it should work but not from my observations.

[jamesedwards]

Yes well I'd hope that was the case and I think that's how it should work but not from my observations.

I'm going to run a quick test...

[jamesedwards]

Yes well I'd hope that was the case and I think that's how it should work but not from my observations.

I'm going to run a quick test...

So I asked Guardian to increment an SV every minute that a market was 'suspended' then increment another SV every minute that the same market was 'closed'.

The increment for 'suspended' worked fine. But once the market closed at 18:15:35, the automation only registered the 'closed' status once, failing to increment any further.

20/05/2025 18:14:28: [G_Auto 1] : Store Value (Shared) for market: closed refresh count = 0
20/05/2025 18:14:28: [G_Auto 1] : Store Value (Shared) for market: suspended refresh count = 0
20/05/2025 18:14:28: [G_Auto 1] : Store Value (Shared) for market: suspended refresh count = 0 + 1 = 1
20/05/2025 18:15:28: [G_Auto 1] : Store Value (Shared) for market: suspended refresh count = 1 + 1 = 2
20/05/2025 18:15:35: [G_Auto 1] : Store Value (Shared) for market: closed refresh count = 0 + 1 = 1


My conclusion is that Guardian indeed, only runs one final sweep through the rulefile once it registers a market as closed.

[sibur]

Thanks for spending the time to analyse. My rule executes once and triggers according to 1 market sv that may be set before or after closure. I think this will mean if the sv is set after closure (by another rule), this rule won't then run. I am at a loss to figure whether I can do anything about this because the rule that changes the sv is set in a completely different BAF.