Skip to content

Add KB: collection scan stuck in Running status #1401

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
hilram7 merged 2 commits into from
Aug 21, 2026
+66 −0
Merged

Add KB: collection scan stuck in Running status #1401

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8aff63e
Add KB: collection scan stuck in Running status
tay-caliguiri Aug 18, 2026
2bf9745
Fix product ID and formatting in collection scan stuck KB article
hilram7 Aug 21, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
66 changes: 66 additions & 0 deletions ...eryad/operations-and-troubleshooting/collection-scan-stuck-in-running-status.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,66 @@
---
description: >-
Shows how to resolve an AD, Entra ID, or Okta collection scan stuck in
Running status in Netwrix Identity Recovery by updating the
TaskInstances table and restarting the Task Server service.
keywords:
- collection scan stuck
- Running status
- TaskInstances
- Task Server
- Entra ID
- Okta
- Active Directory
- Netwrix Recovery for Active Directory
- NetwrixRecovery
- SQL Server Management Studio
- Identity Recovery
- StealthRECOVER
tags:
- kb
- operations-and-troubleshooting
products:
- identityrecovery
sidebar_label: Collection Scan Stuck in Running Status
title: "Collection Scan Stuck in Running Status"
---

# Collection Scan Stuck in Running Status

## Symptom

A collection scan (Active Directory, Entra ID, or Okta) remains in **Running** status indefinitely. The console shows no status details or error messages, and the scan never completes or times out.

## Cause

The scan hung during its collection step. Netwrix Identity Recovery does not apply a timeout to collection work for any of the three scan types, so a stalled directory query, Graph call, or Okta API call leaves the task instance at **Running** with no automatic recovery.

## Resolution

1. In your SQL Server Management Studio instance, locate the Identity Recovery database. The default name is `NetwrixRecovery`.
2. Run a query to find the stuck task instance for the affected task:

```sql
SELECT TOP 1 * FROM TaskInstances WHERE TaskID = '%taskID%' ORDER BY ID DESC
```

3. Update the `Status` column for that row to `8` (Failed):

```sql
UPDATE TaskInstances SET Status = 8 WHERE ID = '%targetID%'
```

4. Restart the `Netwrix Recovery Task Server` service on the Identity Recovery server.
5. In the console, start a new scan for the affected domain, tenant, or org.

## TaskInstances.Status Values

| Value | Meaning |
|---|---|
| 0 | Initialized |
| 1 | Running |
| 2 | Paused |
| 4 | Stopped |
| 8 | Failed/Error |
| 16 | Completed/Finished |
| 32 | Waiting |