Recently we have started to encounter problems with the Report Scheduler in the UMP, at times scheduled reports are skipped / not run.
This appears to be a known issue and is documented under our Report Scheduler Guide.
Some Scheduled Jobs Are Not Running - https://docops.ca.com/ca-unified-infrastructure-management/8-5-1/en/troubleshooting/troubleshooting-report-scheduler#TroubleshootingReportScheduler-SomeScheduledJobsAreNotRunning
If you have multiple large jobs running simultaneously, some jobs may time out. By default, jobs try to execute for 5 minutes. If the job fails to execute within 5 minutes, that job is skipped until the next scheduled run. If this behavior occurs, you can increase the timeout interval by changing the value of the org.quartz.jobStore.misfireThreshold setting in the WEB-INF/classes/quartz.properties file.
You can also try increasing the number of threads that are allowed to execute jobs.
Note: Increasing the number of threads that are used to execute jobs increases the resources that are used by UMP and might cause performance issues.
To increase the number of threads, edit the org.quartz.threadPool.threadCount setting in the WEB-INF/classes/quartz.properties file. The default value is 6.
1. Deactivate the UMP wasp probe.
2. On the UMP server go to: \Nimsoft\probes\service\wasp\webapps\reportscheduler\WEB-INF\classes and open the quartz.properties file.
3. Change the default values to:
4. Save the file and then re-activate the UMP wasp.