Set the Populate Service Account and LDC job stale threshold

task brazil Updated Sep 10, 2026 2 min read configure-sa-ldc-stale-days.md
Raw file servicenow.com

Configure the number of days before a running Populate Service Account and LDC IN CMDB job is considered stale and canceled. Increase this value if a large configuration item (CI) dataset causes the job to be canceled before a full run completes.

Before you begin

Verify that you have at least version 1.30.2 of Discovery and Service Mapping Patterns.

Role required: admin

About this task

The sn_itom_pattern.populate_saldc.stale_job_threshold_days system property controls how long the Populate Service Account and LDC IN CMDB scheduled job can run before the system considers it stale. If the job exceeds this threshold, the system automatically cancels it and starts a new run. The default value is two days. If your instance has many CI records, you can increase this value to give the job more time to complete.

Procedure

  1. In the navigation filter, enter sys_properties.list.

  2. In the Name field, search for sn_itom_pattern.populate_saldc.stale_job_threshold_days.

  3. Select the sn_itom_pattern.populate_saldc.stale_job_threshold_days property.

  4. In the Value field, enter the number of days after which the job is considered stale.

  5. Select Update.

What to do next

Wait for the next scheduled run of the Populate Service Account and LDC IN CMDB job, or execute it immediately. For more information, see Enable direct field population for query performance.

Parent Topic:Improved query performance with direct field population in CI tables

Related topics

Improved query performance with direct field population in CI tables

Enable direct field population for query performance

Trigger a full CI table resync for direct field population

Keywords PopulateSALDCstale job thresholdsystem propertyservice accountlogical data centerCI tables
Search documentation
Search document titles and file paths on the brazil branch