Oracle_jobs and disabled jobs

Hi,

thanks for answering. We’re not sure what the result going forward is. We’ve posed that the behaviour and the documentation do not match, and to create the situation like it is documented needs a separate rule. Is that perceived as a problem? Will the behaviour be altered? Or is the workaround the intended way the situation needs to be resolved?

Best wishes.