---
title: Verify the Microsoft Threat and Vulnerability Management integration import run status
description: Confirm your Microsoft Threat and Vulnerability Management \(MS TVM\) integration runs successfully and locate any issues.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/security-management/vulnerability-response/mstvm-view-import-run-status.html
release: australia
product: Vulnerability Response
classification: vulnerability-response
topic_type: task
last_updated: "2026-07-29"
reading_time_minutes: 1
breadcrumb: [Integration run status, Microsoft Threat and Vulnerability Management, Microsoft Defender Integration for Security Exposure Management, Vulnerability Response integrations, Vulnerability Response, Unified Security Exposure Management, Security Operations]
---

# Verify the Microsoft Threat and Vulnerability Management integration import run status

Confirm your Microsoft Threat and Vulnerability Management \(MS TVM\) integration runs successfully and locate any issues.

## Before you begin

This procedure makes the following assumptions:

-   You have Vulnerability Response and the MS TVM Vulnerability Integration installed and configured.
-   MS TVM Vulnerability Integration imports are scheduled and running.

Role required: sn\_vul.vulnerability\_admin

## About this task

During integration execution, multiple processes are generated, and data is received in pages. Each process can contain one or more import queue entries with attached data in pages. These entries must process the data within a one-hour time limit. If the payload size is large, the processing time may exceed one hour or become stuck, resulting in an integration timeout error. The integration continues to process the data despite the timeout error.

Timestamps \(heartbeats\) are sent periodically to indicate whether 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. If an import queue entry exceeds the one-hour time limit, the system checks the **Last Record Processed** field to determine whether it is also older than one hour. If it is, the import queue entry is stuck and is timed out to prevent further delays in processing.

**Note:** The **Last Record Processed** field is updated based on the following system properties:

-   **sn\_sec\_cmn.record\_threshold\_heartbeat**: Number of processed records after which the heartbeat \(timestamp\) is sent to the import queue entry.
-   **sn\_sec\_cmn.maximum\_heartbeat\_delay**: Time after which the import queue entry is timed out.

## Procedure

1.  Navigate to **All** > **Microsoft Defender Integration for Security Exposure Management** > **Microsoft Threat and Vulnerability Management** > **Integrations**.

2.  Select an integration.

3.  Select the Vulnerability Integration Runs related list.

4.  Verify that the state of the imports is Complete, with the Substate as Success.

    The most common causes for a failed run are:

    -   Network interruption.
    -   Bit decay in the data transfer resulting in corrupted data during the transform.
5.  If you see a failed run occurred, select **Execute now** to rerun the integration.