simple automation fires sometimes but not other times.

Advanced automation available in Guardian - Chat with others and share files here.
Post Reply
Andyx
Posts: 10
Joined: Wed Jun 25, 2025 1:04 am

I set up a very simple win automation file. For 3 races - It fired, it fired, then it didn't fire. Is this a feature of automation software. There was absolutely no reason why it shouldn't fire on this particular race. It's actually quite frustrating.

Any one having a similar experience?

Best regards.
User avatar
Dallas
Posts: 23603
Joined: Sun Aug 09, 2015 10:57 pm

Andyx wrote:
Thu Sep 18, 2025 12:16 pm
I set up a very simple win automation file. For 3 races - It fired, it fired, then it didn't fire. Is this a feature of automation software. There was absolutely no reason why it shouldn't fire on this particular race. It's actually quite frustrating.

Any one having a similar experience?

Best regards.
Every automation rule will fire 100% of the time providing you have configured it and your Guardian settings correctly.

From what you've described it sounds like you have your Guardian refresh rate to low for the number of markets you have loaded and/or your rule/s are armed for
viewtopic.php?t=11491
Andyx
Posts: 10
Joined: Wed Jun 25, 2025 1:04 am

Thanks for the reply - I'll take a read of that - but in the mean time, I've changed the guardian refresh rate to 1 second - it actually was at the fastest- so it may well make all the difference. My logic prevailed faster the better - but clearly not in this case :)
guy333
Posts: 64
Joined: Sun Aug 16, 2015 9:47 am

I have had quite a few instances, in practice mode, where the log shows that Guardian had detected that the market is suspended(preventing rules from firing) but my eyes tell me that the market is not suspended
User avatar
jamesedwards
Posts: 4397
Joined: Wed Nov 21, 2018 6:16 pm

Andyx wrote:
Thu Sep 18, 2025 12:32 pm
Thanks for the reply - I'll take a read of that - but in the mean time, I've changed the guardian refresh rate to 1 second - it actually was at the fastest- so it may well make all the difference. My logic prevailed faster the better - but clearly not in this case :)
Change the refresh rate to the smallest possible latency, should be 20m/s.

At this refresh rate Guardian will cycle at a rate of 50 markets per second. Therefore if you've got 500 markets loaded then each market will refresh approx once every 10 secs. It has to fall on the relevant market at a time when your conditions are met for it to fire.
User avatar
jamesedwards
Posts: 4397
Joined: Wed Nov 21, 2018 6:16 pm

guy333 wrote:
Thu Sep 18, 2025 2:07 pm
I have had quite a few instances, in practice mode, where the log shows that Guardian had detected that the market is suspended(preventing rules from firing) but my eyes tell me that the market is not suspended
Most likely the same issue. Shorten your Guardian refresh rate and/or reduce the amount of markets loaded in Guardian, or load the focus market into one-click or ladder screen to force minimal refresh rate.
Post Reply

Return to “Bet Angel - Automation”