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?