Time Slicing job appears to be hanging


Article ID: 46539


Updated On:


Clarity PPM On Premise Clarity PPM SaaS


The Time Slicing job in Clarity is not completing, it is stuck in the Processing status / taking too long to process. Timeslices are not updated.

Symptoms may include:

  • The Time Slicing job is in the indefinite status of "Processing".
  • The Administration > Data Administration > Time Slices page > "Last Run" column is not being updated for all time slice ids.


One or more of the following could introduce the issue:
  1. PPM SQL trace is enabled per the properties.xml file (traceEnabled="true")
  2. Refreshing from one environment to another
  3. Cancelling a job that is already 'Processing'
  4. Not cleaning up the job scheduler before and after background service starts.
  5. Database and network issues (timeouts,outages,contention


Release: All Supported Releases
Component: Clarity Time Slicing


Step 1: Check if the Time Slicing job instance is progressing via the below query

This applies to On Premise customers. For SaaS customers, please contact Broadcom Support if assistance is needed to confirm if the time slicing job is stuck):

select '(1)assignment PRASSIGNMENT' slice_object, count(*), slice_status from 
PRASSIGNMENT where slice_status in (1,2,3,4) group by SLICE_STATUS 
select '(2)availability PRJ_RESOURCES' slice_object,count(*), slice_status from
PRJ_RESOURCES where slice_status in (1,2,3,4) group by SLICE_STATUS 
select '(3)allocation PRTEAM' slice_object, count(*), slice_status from
PRTEAM where slice_status in (1,2,3,4) group by SLICE_STATUS 
select '(4)timeentries PRTIMEENTRY' slice_object, count(*), slice_status from

It should be processing at a steady pace depending on the object being sliced. If there is no movement, perform the next set of steps.

Step 2: Dedicate all system resources to allow the Time Slicing job to process and complete:

  1. Set all jobs that are WAITING to PAUSED;
  2. Set all jobs that are SCHEDULED to PAUSED;
  3. Set all jobs that are in PROCESSING to CANCELLED
  4. Make note of the scheduled jobs and scheduled times as they will need to be re-entered later.
  5. Delete all CANCELLED job instances
  6. Run an immediate instance of the Time Slicing job to ensure it completes.
  7. Re-enter the jobs that were CANCELLED.

Step 3: Review the bg-ca.logs for any related errors that can help point to root cause

Step 4:  Review related troubleshooting KBs

Review the below KBs for tips, including job incompatibility recommendations that can help in future avoidance of issues with the time slicing job. 

Step 5: On Premise customers - if job is stuck in waiting or scheduled status

If the Time Slicing job is stuck in Waiting or Scheduled status, a restart of the BG service can help.

Additional Information

See also: