---
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


---

# Verify integration run status

# Verify the Microsoft Threat and Vulnerability Management integration import run status {#ariaid-title1}

* Release version: Australia
* 
* Updated July 29, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

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.
{#mstvm-view-import-run-status__ul_qm5_skn_z4b}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.
{#mstvm-view-import-run-status__ul_g23_sgw_dyb}

## Procedure

1. Navigate to AllMicrosoft Defender Integration for Security Exposure ManagementMicrosoft Threat and Vulnerability ManagementIntegrations.
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.
   {#mstvm-view-import-run-status__ul_ucc_mnm_bpb}
5. **Optional:** If you see a failed run occurred, select Execute now to rerun the integration.
{#mstvm-view-import-run-status__steps_wkn_1v4_bkc}

*[\>]: and then