Loading...
Loading...
ServiceNow has identified that the scheduled job Collect Reliability Metrics for Data Management, introduced in the Yokohama release, may contribute to performance degradation in both production and sub-production environments. This job runs daily and estimates table size based on record criteria defined in out-of-box (OOB) rules. These rules target records older than two years in high-volume tables including: • sys_audit (Audit) • sys_email (Email) • task (Task) However, the job executes inefficient SQL queries that filter on non-indexed columns (e.g., tablename in sys_audit). On some instances, this can result in long-running queries, resource contention, and system strain caused by excessive background activity. To mitigate this, ServiceNow is proactively disabling the job across affected environments while a platform-level change is implemented to disable it by default in future releases.
There are no manual steps to reliably reproduce the issue through standard user actions. However, you can verify whether the job is active on your instance by following these steps: 1. Navigate to sys_trigger.list in your instance. 2. Search for the job name: • "Collect Reliability Metrics for Data Management" 3. Open the job record and review the following fields: • Trigger Type: If the value is "Disabled", the job is not currently scheduled to run. • Run Time: Displays the scheduled execution time (e.g., 01:00:00) • Next Action: Displays the next scheduled run if the job is still active. NOTE: Even if the job is scheduled during a non-peak time, it may still contribute to performance degradation due to inefficient query patterns.
This problem is currently under review and targeted to be fixed in a future release. Subscribe to this Known Error article to receive notifications when more information becomes available. To reduce the risk of performance degradation in the meantime, ServiceNow is proactively disabling the Collect Reliability Metrics for Data Management job on instances where it is currently active. If your instance is included in this maintenance, you'll receive a notification with your scheduled window. FAQ Q: What is the impact of this issue? A: Affected instances may experience database performance degradation, including slow queries, delayed responses, or resource strain. Q: Does this issue affect production instances, sub-production instances, or both? A: Both. The job is enabled by default in all environments running the Yokohama release (below Yokohama Patch 7). Q: Are both production and sub-production instances being targeted with this maintenance? A: Yes. This round of maintenance includes all environments to ensure consistent disablement of the scheduled job. Q: What is the criteria for targeting an instance with this maintenance? A: All Yokohama and later instances where the scheduled job is still active are included. Q: What does the maintenance involve? A: ServiceNow will disable the job by updating its trigger configuration to prevent it from executing. Q: When will this maintenance happen? A: Maintenance is scheduled for August 2025. If your instance is included, you will receive a notification with your specific window. Q: Will there be any service impact? A: No. The update is lightweight, takes less than five minutes, and does not cause downtime or interfere with in-progress activities. Q: I have an activity scheduled during the maintenance window (e.g., a deployment). Will this interfere? A: No. This maintenance is non-intrusive and does not conflict with deployments, upgrades or other scheduled work. Q: Can I opt out of this maintenance? A: Yes. If you prefer to manage this change independently, you may opt out via the Communication Record. Q: Can I conduct this maintenance myself? A: Yes. A customer admin can disable the job manually via the job record in the sys_trigger table. Q: What happens if I opt out of this maintenance? A: If you choose to opt out, the job will remain active on your instance until it is disabled by default in a future release or you choose to disable it manually. Please be aware that leaving the job active may result in performance degradation. Q: Will this change be carried over if my instance is cloned or upgraded? A: In some cases, a clone or upgrade could reintroduce the job in an active state. After such activities, you may wish to verify that the job remains disabled, as noted in this article. Q: Where can I track the status of this Known Error? A: You can subscribe to this Known Error article to receive notifications as new information becomes available, including updates on the permanent fix and release schedule. Q: What is the permanent fix? A: The job is planned to be disabled by default in a future platform release. Q: Which versions will contain the permanent fix? A: Zurich and Yokohama Patch 7+. Q: Do I need to do anything after the patch is applied? A: No action is required. However, if your instance is later cloned or updated, you may wish to verify that the job remains disabled.
PRB1908446
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.