Oracle_jobs and disabled jobs

[foobar]

Hi @JacksonPollack

@JacksonPollack

As far as I can see, the table queried is cdb_scheduler_jobs.

correct!

@JacksonPollack

We can see multiple ways to improve the situation:

• Not querying disabled jobs (ENABLED field in cdb_scheduler_jobs): There is no expectation of finding out any state of a non-running job
• Having disabled jobs in the state of OK always, when and if there is no information about their last execution available from cdb_scheduler_job_run_details. If the job was executed at least once and has information logged in cdb_scheduler_job_run_details, but is now disabled, react to that information accordingly.

Both options sound valid and I can see why I would have a usecase for both.