Scan Stuck on "Running" for Hours

Symptoms: The Scanning tab shows “Running” status and the progress bar does not advance for more than an hour.

Causes:

1. A stale orchestrator started a scan that is no longer processing (the async consumers have stopped).
2. Multiple concurrent scan runs were started (overcounting issue fixed in v4.9).

Fix:

1. Navigate to Admin Settings → System tab. Check the content-scan job row. If it shows “running” for more than 4 hours, the scan epoch has likely stalled.
2. Return to the Scanning tab and click Pause to stop the scan.
3. Wait 30 seconds, then click Resume or start a fresh scan.
4. If the status does not update, check Forge logs (forge logs) for error messages from the scan-content consumer.