---
sourceDocument: Australia Security Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/security-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Security Management

ft:clusterId :

    - security

bundleId :

    - security

workflow :

    - Technology


---

# View the (National Vulnerability Database) NVD integration import run status

# View the (National Vulnerability Database) NVD integration import run status {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Use the Vulnerability Integration Runs related list to verify
the success of your integration runs, locate any issues, and inform your remediation
decisions.

## Before you begin

To view the NVD integration import run status:

* Vulnerability Response and the Vulnerability Response integration with NVD integration application must be installed and configured.
* The NVD integration imports must be running. The NIST National Vulnerability Database Integration-API (CVE only) integration runs by default.  
  Note:  
  The NIST National Vulnerability Database Integration-API (CPE only) and the NIST National Vulnerability Database Integration-API (Unmapped CPE) integrations are inactive by default. See [Activate the NIST National Vulnerability Database--API (CPE only)](https://servicenow-prod.fluidtopics.net/tv6~nhoCd~2oDYSHAh_Kmw#activate-nist-nvd-cpe-only-integration "To ingest Common Platform Enumeration (CPE) data, you can perform a full data import with a daily scheduled job.") and [Activate the NIST National Vulnerability Database--API (Unmapped CPE)](https://servicenow-prod.fluidtopics.net/tv6~nhoCd~2oDYSHAh_Kmw#activate-nist-nvd-unmapped-cpe "To ingest Common Platform Enumeration (CPE) data for fetched Common Vulnerabilities and Exposures (CVE) data, you can perform a full data import with an on-demand scheduled job.") for more information.
{#nvd-check-imports__ul_z5l_rhn_wcb}

Role required: sn_vul.vulnerability_admin or App-Sec Manager

## About this task

During integration execution, multiple processes are generated, and data is received in the form of pages. Each process can contain one or more import queue entries with attached data in pages. These entries must process the
data within the one-hour time limit. However, if the payload size is large, the processing time may exceed one hour or get stuck, resulting in an integration timeout error. The integration continues to process the data despite
the timeout error.  
To avoid this miscommunication, starting from version 18.2.4 of Vulnerability Response, timestamps (heartbeats) are sent periodically to indicate if the queue is active and processing data. The Last Record Processed field in the Import Queue Entry page is updated based on the count of records the import queue creates or updates. In case an import queue entry exceeds the one-hour time limit, the system checks the Last Record Processed field to see if it's also older than one hour. The last record processed being older than an hour indicates that the import queue entry is stuck, and it's timed out to prevent any further delays in processing.  
Note:  
The Last Record Processed field is updated based on what is defined in the following system properties:

* sn_sec_cmn.record_threshold_heartbeat: Defines the number of processed records, after which the heartbeat (timestamp) is sent to the import queue entry.
* sn_sec_cmn.maximum_heartbeat_delay: Defines the time after which the import queue entry must be timed out.
{#nvd-check-imports__ul_g23_sgw_dyb}

## Procedure

1. If you aren't using the NVD integration run status chart, Navigate to AllVulnerability Response or Application Vulnerability ResponseAdministrationIntegrations.
2. Select a link for an integration.
3. Select the Vulnerability Integration Runs related list.
4. Verify that all imports have succeeded.  
   The most common causes for a failed run include:
   * Network interruption.
   * An issue in the data transfer resulting in corrupted data during the transform.

   {#nvd-check-imports__ul_ecy_cnn_xcb}If you encounter any of these conditions, select Execute Now, and rerun the integration.
**Related reference**   

* [Vulnerability Response vulnerability form fields](https://servicenow-prod.fluidtopics.net/X3YBvFahBIyD8JZVGA06cw "Vulnerabilities are created automatically when records are downloaded from the National Vulnerability Database (NVD), Common Weakness Enumeration (CWE), or third-party integrations and stored under Libraries in Vulnerability Response.")

*[\>]: and then