Skip to main content

General Trouble Shooting

Overview

This guide explains how to troubleshoot partially successful or failed scans in DeepTraQ. Understanding scan status and reviewing error logs are essential to identify issues, resolve failures, and ensure accurate security assessments.

Scan status is indicated by icons in the dashboard:

  • Green icon (Done) – Scan executed successfully.
  • Yellow icon (Partially Completed) – At least one job succeeded and at least one job failed.
  • Red icon (Failed) – Scan execution failed; the security scanners were unable to complete checks.
  • Gray icon (Stopped) – Scan was manually stopped by the user.

Hovering over the icons shows the corresponding status message.

Only partially successful or failed jobs provide detailed error logs to help diagnose problems.


Supported Platforms

This troubleshooting guide applies to all scan types supported by DeepTraQ, including:

  • Network Perimeter scans
  • Web Application scans
  • Code scans

Error logs and diagnostic steps are consistent across all scan types.


Prerequisites

  • Access to the DeepTraQ dashboard
  • Scan project created
  • Appropriate permissions to view scan history and error logs

Understanding Scan Status

StatusIcon ColorDescription
DoneGreenScan completed successfully; all jobs executed without errors.
Partially CompletedYellowAt least one job succeeded and at least one job failed.
FailedRedScan execution failed; security scanners were unable to complete checks.
StoppedGrayScan was manually stopped by the user.
Submit ErrorRed with “Submit Error”Job was not successfully added to the security scanners.

Viewing Scan History and Errors

Error logs provide diagnostic information without exposing sensitive data. Use the following steps:

  1. Navigate to the scan project in the Findings Dashboard.
  2. Click the History tab to view all historical scans for the selected project.
  3. Review the Status column to identify partially completed or failed scans.
  4. Open the three-dot menu next to a scan.
  5. Click Error to view detailed logs.
  6. If multiple errors exist, click the arrow button to expand all details.

Errors typically indicate:

  • Temporary processing issues
  • Configuration or connectivity problems
  • Scanner execution failures

If problems persist after retrying, contact support for assistance.


Debugging Steps

  1. Verify the scan targets are reachable and correctly configured.
  2. Check the scan profile and authentication settings if applicable.
  3. Review the expanded error logs for details on the failure.
  4. Retry the scan after addressing any issues found in the logs.
  5. If issues remain unresolved, escalate to support with the relevant error logs.

Following these steps ensures that partially completed or failed scans can be effectively diagnosed and resolved.


  • Understanding Scan Status
  • Debugging Failed Jobs
  • Network Perimeter Scanning
  • Investigating Web Application Vulnerabilities