What causes jobs to go into a Not Scheduled status?
Article ID: 104100
Updated On:
Products
Clarity PPM SaaS
Clarity PPM On Premise
Issue/Introduction
What would cause a job to go into a status of "Not Scheduled"?
Environment
Release:
Component: PPMBPM
Component: PPMBPM
Resolution
Prior to 15.3, if a scheduled job was processing, and during the time which it was processing, the BG server went down or was restarted, the job that was in process would go into a "Not Scheduled" status.
In 15.3, the Job Monitor functionality was delivered which monitors all running jobs and keeps a thread open, so that if this condition were to occur where the BG server fails or was recycled, the job would re-start on its own because the Job Monitor is tracking the threads. This prevents the problem from occurring.
In 15.3, the Job Monitor functionality was delivered which monitors all running jobs and keeps a thread open, so that if this condition were to occur where the BG server fails or was recycled, the job would re-start on its own because the Job Monitor is tracking the threads. This prevents the problem from occurring.
Feedback
Yes
No
Powered by
