This is caused by a disruption in the job scheduler, which runs on the background (BG) service. If the jobs were not paused and/or were not allowed to complete prior to the disruption, the job scheduler will not recover.
- Any action such as the below will affect the Clarity job scheduler running on the BG service.
- Server upgrades
- Database refreshes
- Connection issues
- Patch installs will
- There is a chance that after a release update the jobs that were in flight (i.e. in the Processing status) will be orphaned. Therefore, they will appear as never completing. This can then force the Clarity administrator on the customer side to cancel, delete, and re-enter the job. In some instances, scheduled jobs may no longer run.
- For SaaS customers: As the SaaS team will not be performing the actions to reschedule or re-enter jobs in the event the issue occurs, it is highly recommended to pause all jobs in the Waiting and Scheduled states prior to the release update activity.
- For On-Premise customers: Please check with your internal IT team for any maintenance performed recently that could have caused a disruption to the BG service.