We have recently refreshed database from production to Dev. We have observed that time slice job is not running however in production its working fine without any issues. Any clues why the same time slice job is not working in Dev.
Any inputs will be highly appreciated.
Please be noted, we do not have access to app logs. Restarted BG services but issue still persist.
You could try removing the existing time slice job instance and submitting another new one?
(assuming the instance of the timeslice job is one that has been copied over from production)
Otherwise - are other jobs running OK?
It sounds like an instance of Timeslicing job got stuck as still running in the scheduler. This happens when a warm backup was performed instead of cold one, and jobs were still running in Clarity. We always recommend all jobs to be paused whilst a backup is taken for refreshing another environment.
Please try the following:
1. Check the existing scheduled Timeslicing, take a screenshot / write down the schedule2. Cancel and delete all instances of Timeslicing job3. Restart bg services4. Try scheduling a Timeslicing job in immediate mode.5. If it works, use the screenshot from step 1 to reschedule the job as it was.
If the above steps to do not solve the issue, please use the solution from the technical article below:
Nika HadzhikidiCA TechnologiesPrincipal Support Engineer