View the Integrations for Central Vulnerability Database Import Run Status

  • Release version: Zurich
  • Updated March 28, 2026
  • 1 minute to read

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

    Before you begin

    Before viewing the EUVD integration import run status, meet the following prerequisites:

    • Vulnerability Response Integration Framework, Central Vulnerability Database, and the Integrations for Central Vulnerability Database application must be installed and configured.
    • The related Integrations for Central Vulnerability Database imports must be running.
    Note:
    The ENISA EUVD and JVN integrations are inactive by default. Activate each integration before checking run status.

    Role required: sn_vul_int_fw.read_integrations or sn_vul_int_fw.configure_integrations

    About this task

    During integration execution, the system generates multiple processes and receives data in the form of pages. Each process can contain one or more import queue entries with attached data in pages. These entries must process data within the one-hour time limit. However, if the payload size is large, the processing time may exceed one hour or stall . This results in an integration timeout error. The integration continues to process the data despite the timeout error.

    To avoid this issue, the system sends heartbeat timestamps periodically to indicate whether the queue is active and processing data. The system updates the Last Record Processed field in the Import Queue Entry page based on the count of records the import queue creates or updates. If an import queue entry exceeds the one-hour time limit, the system checks the Last Record Processed field age. If the field is also older than one hour, the system considers the import queue entry stuck and times it out to prevent further delays.

    Note:
    The system updates the Last Record Processed field based on 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.

    Procedure

    1. In the Filter Navigator search bar, enter sn_vul_int_fw_integration.LIST and press Enter.
    2. Select a link for the integration you want to review.
    3. Select the Vulnerability Integration Runs related list.
    4. Verify that all imports have succeeded.
      Note:
      The most common causes for a failed run include:
      • Network interruption.
      • An issue in the data transfer resulting in corrupted data during the transformation.

      If you encounter any of these conditions, select Execute Now to rerun the integration.