Loading...
Loading...
ServiceNow previously identified that the Physical Table Monthly Stats Aggregator and Physical Table Yearly Stats Aggregator scheduled jobs could contribute to performance degradation in some environments. These jobs were configured to run at 08:00 or 09:00 UTC across thousands of production and sub-production instances, resulting in CPU load spikes, resource contention, and sluggish performance on shared database infrastructure. To mitigate this, ServiceNow introduced randomized start times in Xanadu Patch 7 and Yokohama Patch 1, and conducted multiple rounds of proactive maintenance during March, April, and May 2025 to ensure proper configuration in environments where the fix was not consistently applied (e.g., due to certain upgrade paths or instance cloning events). However, monitoring of the June 1 job run confirmed that staggered execution alone did not fully resolve the issue. The job’s underlying queries continued to impose significant strain on the database, leading to a spike in high-severity performance cases. As a precautionary measure to maintain instance stability, ServiceNow conducted an additional round of proactive maintenance to disable both the Monthly and Yearly Stats Aggregator jobs across all customer environments. These jobs will remain disabled by default moving forward. An optimized replacement will be evaluated for future platform releases.
This issue is caused by the Physical Table Monthly Stats Aggregator and Physical Table Yearly Stats Aggregator jobs, which can generate high CPU load on shared database infrastructure. While randomized start times were previously introduced, they have proven insufficient due to the complexity of the underlying queries. There are no manual steps to reliably reproduce the issue. However, you can check whether the jobs are active on your instance: 1. Navigate to sys_trigger.list 2. Search for: a. "Physical Table Monthly Stats Aggregator" b. "Physical Table Yearly Stats Aggregator" 3. Open each job record and review: a. trigger_type: "2" = Disabled b. run_time: "08:00:00" or "09:00:00" UTC indicates default (non-randomized) timing c. next_action: Shows the next scheduled execution time Note: Even if the job appears to have a randomized run time, it may still contribute to elevated database load during execution. As a result, ServiceNow is disabling these jobs on all instances until a more optimized version is delivered in a future release.
This problem was previously identified and addressed through proactive maintenance ahead of the June 1, 2025 job run. ServiceNow applied updates across affected instances to mitigate performance impact from the Physical Table Monthly Stats Aggregator and Physical Table Yearly Stats Aggregator jobs. Randomized start times had initially been introduced in Xanadu Patch 7 and Yokohama Patch 1, and multiple rounds of proactive maintenance were performed in March, April, and May 2025 to ensure configuration consistency. However, monitoring of the June 1 job run confirmed that staggered execution alone did not fully resolve the issue. As a precautionary measure, ServiceNow completed an additional round of proactive maintenance to disable both jobs across all customer environments to maintain instance performance and stability. These jobs will remain disabled by default moving forward. FAQs Q: What was the impact of this issue? A: Affected instances experienced slow performance, delayed database responses, or timeouts due to high CPU load on shared infrastructure. Q: Which instances were targeted with this maintenance? A: Both production and sub-production instances were included in the final round of maintenance. Q: What did the maintenance involve? A: ServiceNow disabled the Monthly and Yearly Stats Aggregator jobs to prevent simultaneous execution and reduce database strain. Q: When was this maintenance completed? A: The final round of maintenance was completed prior to the June 1, 2025 job run. Q: Will there be any service impact from this change? A: No. The updates took less than five minutes per instance, with no downtime or disruption. Q: Can customers re-enable these jobs manually? A: ServiceNow strongly advises against re-enabling these jobs.
PRB1885210
Click on a version to see all relevant bugs
ServiceNow Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.