v 5.6.12
Hey,
This is just an informational post since I found the issue and resolved the problem.
But a word of warning, and maybe the mechanism can be improved on this in future.
I updated my computer group name to make more sense (I have one node for a script runner and one as a web node, each node is assigned to their own computer group respectively).
Anyway, I searched for all references in my code base and replaced the name throughout. Then went on annual leave for a week. Only to come back and find the scheduler was not running for the majority of my jobs.
The reason was because I persist my schedules to the database so they weren’t in the codebase and still had the old name/computer group referenced. Some of them were NULL and using the default (which was still working) and looked fine when I tested to see if jobs were still running.
Maybe just something simple like a notification/warning might help if a schedule is triggered but there’s no matching computer group configured, or node available to run the job it should flag an issue and make it obvious to anyone who logs in?