Some of the jobs get stuck in PROCESSING status in the CMN_SCH_JOBS table without having a corresponding record in CMN_SCH_JOB_RUNS.
This behavior causes no new jobs getting triggered for those that are stuck in Processing status. At the same time, it is also observed that records are left behind in CMN_SCH_JOB_LOGS.
Steps to Reproduce:
Expected Results: It should not leave jobs in Processing status.
Actual Results: It leaves jobs in Processing status.
Clarity 16.2.3, 16.3.0
DE160990
This issue is fixed in Clarity 16.3.1 and 16.2.3.3 (16.2.3 Patch 3)
Workaround: Restart BG service.