---
sourceDocument: Brazil IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/it-operations-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Set the stale job threshold

# Set the Populate Service Account and LDC job stale threshold {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
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{#configure-sa-ldc-stale-days__configure-sa-ldc-stale-days-prereq-p1}

## 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.{#configure-sa-ldc-stale-days__configure-sa-ldc-stale-days-context-p1}

## Procedure

1. In the navigation filter, enter <kbd class="ph userinput">sys_properties.list</kbd>.
2. In the Name field, search for <kbd class="ph userinput">sn_itom_pattern.populate_saldc.stale_job_threshold_days</kbd>.
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](https://www.servicenow.com/docs/p7Vp1OAHkD4C7xGTSNwtFQ "Populate Service Account, Logical Datacenter, and Virtual Machine Object fields in configuration item (CI) tables to improve query performance.").
**Related concepts**   

* [Improved query performance with direct field population in CI tables](https://www.servicenow.com/docs/v2LqO55fNZJKQV3ctb~rBg "The Populate Service Account and LDC IN CMDB scheduled job populates the Service Account and Logical Datacenter fields in cloud configuration item (CI) tables, and the Virtual Machine Object field in the Hardware [cmdb_ci_hardware] table. This direct population reduces query complexity and improves query performance.")  
**Related tasks**   

* [Enable direct field population for query performance](https://www.servicenow.com/docs/p7Vp1OAHkD4C7xGTSNwtFQ "Populate Service Account, Logical Datacenter, and Virtual Machine Object fields in configuration item (CI) tables to improve query performance.")
* [Trigger a full CI table resync for direct field population](https://www.servicenow.com/docs/GUtCpoK8VU1wUtCsyHZW9Q "Trigger the Populate Service Account and LDC IN CMDB scheduled job to reprocess all configuration item (CI) records. Configure the sn_itom_pattern.populate_saldc_full_resync system property when service accounts or logical datacenters have incorrect or corrupted values for a CI.")