This isn't a batch scheduling problem. It's a monitoring and alerting problem. OP needs a monitoring and alerting solution.
Stop ~~~ engineering ~~~ things and choose the right tool for the job.
Stop ~~~ engineering ~~~ things and choose the right tool for the job.
A large portion of the cost of many of these tools is spent "choosing the right tool for the job" Figuring out what they do, what they do well, where they overlap, where the company that makes the tool is headed, how hard its going to be to swap that tool out for a better one (or cheaper one) - thats a lot of expense in labor and training.
I claim using pretty much any tool other than jenkins is easier to maintain over time (as illustrated in this very article).