Disappointing log really; it doesn’t mention anything about executing your rule or scheduling the next run.
I expected at least to see
Calling execute on "some rule" … the lack of that is odd.
TRACE logging level would give us more, but I think perhaps you have a busy system and this extra work might throw more side effects. I note there is some jumbling of order in the log snippet, suggesting a fair bit of traffic from time to time at least.
However, poking around in old similar github issues, quartz may be the wrong place to look. It’s being the “clock” but something else does the scheduling. All terribly complicated, lists of candidates for scheduling, beyond me.
That used to be org.eclipse.smarthome.core.scheduler - but I’m guessing that is renamed in 2.5M2?? Need some proper developer advice here I think.