Troubleshoot Long-Running Scans

Use this guide when the Optimizer identifies a Scan that is taking longer than expected.

A long-running Scan does not always mean that something is wrong. Scan duration can be affected by the size of the Scan, target response time, Repeater performance, and execution configuration.

1. Review the Scan scope

Large Scans can take longer to complete.

Check:

The number of entry points included in the Scan.
Whether the Scan scope recently increased.
Whether the Scan includes more tests than previous executions.

If the Scan is unusually large, consider reducing the scope or splitting it into smaller Scans.

Large executions can also consume more engine memory. If the Scan fails with a memory-related error, reduce the number of entry points or split the Scan before starting a new execution.

2. Check target responsiveness

Slow or unstable target responses can increase Scan duration.

Check:

Application response time.
Network latency.
Connection timeouts.
TLS errors.
Firewall or WAF rate limits.

If the target temporarily becomes unavailable or stops responding, Bright may pause or disrupt the execution depending on the error.

3. Check Repeater performance

If the Scan uses a Repeater, verify that the Repeater is stable and has enough resources.

Check:

Repeater connection status.
CPU and memory usage on the Repeater host.
Network stability.
Outbound connectivity to Bright.
Connectivity from the Repeater to the target.

A Repeater that becomes overloaded or stops responding can delay or disrupt an execution.

4. Review Scan configuration

Review the Scan configuration and confirm that it matches the intended scope.

Check:

Selected tests.
Entry point configuration.
Dynamic entry point filters.
Authentication Objects.
Uploaded files or integration data used to build the Scan scope.

Incorrect or unexpectedly broad configuration can affect the execution.

5. Check whether the Scan is still progressing

Review the Scan execution details.

If the Scan is still processing entry points and making progress, it may simply require more time.

If the Scan stops reporting status for an extended period, Bright may terminate it as a timed-out execution. If this happens, retry the Scan once. If the same problem occurs again, contact Bright Support.

When to contact Bright Support

Contact Bright Support if:

The Scan stops progressing.
The Scan repeatedly times out.
The engine repeatedly fails or restarts.
A normal-sized Scan repeatedly runs out of memory.
The Scan remains unusually slow after target, Repeater, and configuration checks.

Include the Scan ID, the approximate start time, and any relevant information about the Scan scope, target, and Repeater.