general question: always triggering

a general question:

as we can see in the trigger logs, a trigger is ALWAYS (every second!) detecting (if the conditions are met) when monitoring is on. that consumes a lot of CPU and its often superfluous.

shouldnt it be possible to decide which trigger detects or not and when and when not? I know, there is a function: "no triggering till.." but this is often useless.

e.g. you have an overall trigger for greyhounds and soccer. why should the soccer-trigger detect all day long the monitored greyhounds markets when the soccer matches will begin in the evening? you cant check "no triggering till.." because you need to trigger the greyhounds markets all day long.

of course, you could create different profils. but that is not the solution: 3-4-5 profiles at the same time would not work correctly because of the limited api-calls.

what do you think?

Hi
A few ideas:

Have a look at trigger actions:
activate trigger/block
deactivate trigger/block
set market's idle refresh to

for example:
set default idle refresh in settings to 300 secs
trigger:
set market's idle refresh to 2 secs
condition:
market's minutes before the off is less than 10

you can sort My Markets by date and time
and adjust refresh rate for first x markets using market_index

you can also use the scheduler to load markets at appropriate times.

thx for the ideas, very useful.

why should the soccer-trigger detect all day long the monitored greyhounds markets when the soccer matches will begin in the evening?

Why indeed? Set the "Markets" to "Soccer Games" where the trigger should operate in football matches and "Greyhound races" where it should bet on greyhounds.

yes, thats already done.
but the trigger e.g soccer doesnt have to detect anytime if the market turned/monitored on is a soccer-market?

Mmm.. not sure what you mean? If a market is already being monitored, then discarding it as a wrong type of market for a particular trigger takes milliseconds.