Jobs in "Waiting" status do not move to "Processing" when the JS Heart Beat job is not scheduled to run
search cancel

Jobs in "Waiting" status do not move to "Processing" when the JS Heart Beat job is not scheduled to run


Article ID: 7192


Updated On:


Clarity PPM SaaS Clarity PPM On Premise


After an incompatible job completes, it never picks up that that job that was in Processing has completed, so the next job never runs.

Steps to Reproduce

  1. Go to Home > Jobs
  2. Submit the Datamart Extraction job in immediate mode.
  3. The job goes into a "Processing" state
  4. Also, submit the Delete Investments job in immediate mode
  5. This job goes into "Waiting" status, because it is incompatible with the Datamart Extraction job.
  6. Wait for the Datamart Extraction job to complete, then check the Delete Investments job status

Expected Result: The Delete Investments job moves to "Processing" status, because the incompatible job that was running has now been completed.

Actual Result: The Delete Investments job goes into "Scheduled" status and does not run 


Release: All Supported


The JS Heart Beat job is not scheduled in the environment.

The query below will tell you if the job is scheduled to be run.

select job_id,, sj.is_visible
from CMN_SCH_JOBS sj
    inner join CMN_SCH_JOB_DEFINITIONS sjd on
    and sjd.job_code='job_check_heart_beat'

If no results are returned the job has possibly been deleted.


On Premise customers:

  1. Connect to the Claritydatabase, and backup the CMN_SCH_JOB_DEFINITIONS table.
  2. Execute the following query to temporarily update the visibility of this job:

    update cmn_sch_job_definitions set is_admin_visible = 1 where job_code ='job_check_heart_beat' ; commit ;
  3. Log in to the application as an administrator user
  4. Navigate to Administration, Data Administration: Reports and Jobs
  5. Filter and find in the list the job called JS Heartbeat
  6. Schedule it to run recurrently every month, every day and every minute (if you use cron format it will be * * * * *)
  7. Save the new scheduled instance
  8. Once it is scheduled in the application, please disable the job visibility back on the database level:

    update cmn_sch_job_definitions set is_admin_visible = 0 where job_code ='job_check_heart_beat' ; commit ;

SaaS customers

Open an issue with Broadcom support for assistance