Workflow guide

Troubleshoot a run

Isolate the failure and prepare a useful, redacted support request.

Editorial review: · Mindtro product documentation

Confirm the enabled version and permissions in your environment. These guides do not announce a general release.

Before you start

An authorised target, working connection, a selected policy and permission to start scans. Use a test environment and a bounded budget for the first run.

Steps

  1. For a failed scan, inspect target availability, preflight, budgets and worker state. Keep failed or skipped checks distinct from clean findings.
  2. Compare the observed outcome with the expected result. Keep the relevant identifier and a redacted record so a colleague can review the same case.
  3. Provide the timestamp, product/environment version, expected and observed result, and a redacted request or run identifier. Remove credentials and personal data.

Check the result

Compare the observed outcome with the expected result. Keep the relevant identifier and a redacted record so a colleague can review the same case.

If it does not work

For a failed scan, inspect target availability, preflight, budgets and worker state. Keep failed or skipped checks distinct from clean findings.

Contact our team →

← Pyrodit Scan Lab
Troubleshoot a run | Mindtro | Intelligence, Engineered