Troubleshoot Scan and Discovery Execution Issues

Use this guide when a Scan or Discovery fails, becomes disrupted or incomplete, or pauses because of an execution issue.

The Optimizer groups these problems under Execution Issues. Open the execution error details to see the specific error message and error code.

Important: If an execution is Paused with an error, fix the underlying issue and resume it. For terminal states such as Failed, Disrupted, or Incomplete, fix the issue and start a new execution.

Repeater issues

Repeater not found

Related error: repeater_not_found

The selected Repeater no longer exists or does not belong to your organization.

What to do

1. Open the Scan or Discovery configuration.
2. Select an existing, active Repeater.
3. If you use the API, verify that the Repeater ID is correct.
4. Start a new execution.

The issue is resolved when the execution passes validation and starts.

Repeater is not connected

Related error: repeater_not_connected

The selected Repeater exists, but it was offline when the execution tried to start.

What to do

1. Start the Repeater service.
2. Wait until the Repeater shows as connected.
3. Start a new execution.

Repeater belongs to another project

Related error: wrong_repeater

The selected Repeater is not assigned to the project used by the Scan or Discovery.

What to do

1. Assign the Repeater to the correct project, or select a Repeater that is already assigned to it.
2. Start a new execution.

Repeater disconnected during execution

Related error: repeater_disconnected

The Repeater went offline while the execution was running. This can happen if the Repeater host shuts down, loses network connectivity, or the Repeater process stops.

What to do

1. Confirm that the Repeater host is running.
2. Check its network connection.
3. Check whether the Repeater service crashed or restarted.
4. Start a new execution.

If the problem continues, provide Bright Support with the Repeater ID, disconnect time, and relevant host logs.

Repeater stopped responding

Related error: repeater_timeout

The Repeater stopped responding for an extended period during the execution.

What to do

1. Check CPU and memory usage on the Repeater host.
2. Verify outbound connectivity from the Repeater to Bright.
3. Check firewall rules that may block the connection.
4. Start a new execution.

If the problem continues, provide Bright Support with the Repeater ID and relevant host resource or network logs.

Repeater connection became unstable

Related error: engine_bridge_connection_failed

Too many requests through the Repeater failed during the execution. Bright pauses the execution instead of terminating it.

What to do

1. Verify that the Repeater is connected and stable.
2. Confirm that the Repeater can reach the target.
3. Fix any network or Repeater issues.
4. Resume the existing execution.

---

Target connectivity issues

Target hostname cannot be resolved

Related error: engine_target_dns_error

Bright repeatedly failed to resolve the target hostname during the execution. The execution is automatically paused.

What to do

1. Verify that the hostname resolves from the network used by the Bright engine or Repeater.
2. Check DNS configuration.
3. If applicable, check private DNS, split-horizon DNS, or VPN access.
4. Resume the existing execution.

Target stopped responding

Related error: engine_target_not_responding

Bright received repeated connection timeouts, refused connections, or TLS errors from the target. The execution is automatically paused.

What to do

1. Confirm that the target is available.
2. Check target response time and latency.
3. Check the TLS certificate.
4. Check firewall or WAF rules and rate limits.
5. Resume the existing execution.

Target is unavailable

Related error: engine_target_down

The target is unreachable.

What to do

1. Confirm that the application is running.
2. Verify that the target is reachable from the Bright engine or Repeater network.
3. Check network and firewall configuration.
4. Start a new execution.

Bright traffic is blocked by a firewall

Related error: engine_firewall_exception_missing

Bright cannot reach the target because scan traffic is blocked by a firewall.

What to do

1. Review the firewall rules protecting the target.
2. Allow Bright scan traffic from the required source IP addresses.
3. Confirm that the target is reachable.
4. Start a new execution.

---

Target authorization issues

Target is not authorized

Related error: target_unauthorized

The target host is not included in your organization's authorized or verified hosts.

What to do

1. Authorize and verify the target host.
2. Start a new execution.

Authentication Object target is unreachable

Related error: ao_target_not_reachable

The target configured in the Authentication Object could not be reached during validation.

What to do

1. Verify that the Authentication Object uses the correct target URL.
2. Confirm that the target is running and reachable.
3. Check whether a firewall is blocking Bright traffic.
4. Start a new execution.

---

Authentication Object configuration issues

An Authentication Object defines how Bright authenticates to a protected application.

Authentication Object does not exist

Related error: ao_not_exists

The configured Authentication Object no longer exists or the referenced ID is invalid.

What to do

1. Select a valid Authentication Object.
2. Start a new execution.

Authentication Object has no project

Related error: ao_no_project

The Authentication Object is not associated with a project.

What to do

1. Associate the Authentication Object with the correct project.
2. Start a new execution.

Authentication Object belongs to another project

Related error: ao_project_mismatch

The Authentication Object belongs to a different project than the Scan or Discovery.

What to do

1. Select an Authentication Object from the same project as the execution.
2. Start a new execution.

---

Scan configuration issues

Scan configuration is invalid

Related error: scan_config_failure

The Scan configuration did not pass validation. This can happen when the selected tests and Authentication Objects do not match the Scan configuration, when no valid tests remain, or when the entry point configuration is invalid.

What to do

1. Review the selected tests.
2. Review the Authentication Objects assigned to the Scan.
3. Review the entry point configuration.
4. Correct the configuration and start a new Scan.

No valid tests are available

Related error: scan_tests_empty

No valid tests remain for the Scan.

What to do

1. Review the tests selected in the Scan configuration.
2. Select tests that are available for your plan.
3. Start a new Scan.

A selected test is unavailable

Related error: scan_test_unavailable

One or more configured tests are no longer available. In some cases, the Scan may continue without the unavailable test and show a warning.

What to do

1. Review the selected tests.
2. Remove or replace unavailable tests.
3. Start a new Scan if required.

No entry points match the Scan configuration

Related error: no_dynamic_entrypoints

The Scan uses dynamic entry points, but no entry points match the configured status filter.

What to do

1. Review the entry point status filter.
2. Broaden the filter if appropriate.
3. If the project does not contain the expected entry points, run a Discovery first.
4. Start a new Scan.

Uploaded file contains no usable target

Related error: scan_target_missing

The uploaded HAR or OAS file does not contain a usable target URL.

What to do

1. Verify that the uploaded file contains valid, parseable target URLs.
2. Upload the corrected file.
3. Start a new execution.

Referenced file does not exist

Related error: file_not_exist

The file referenced by the execution was deleted or its ID is invalid.

What to do

1. Select an existing file.
2. Start a new execution.

File belongs to another project

Related error: wrong_project_file

The selected file belongs to a different project.

What to do

1. Select or upload a file that belongs to the same project as the execution.
2. Start a new execution.

---

Integration issues

Bright cannot access the Snyk integration

Related error: integration_access_error

Bright could not access the configured Snyk integration because of an authentication or authorization problem.

What to do

1. Verify the Snyk credentials.
2. Verify that the integration has the required permissions.
3. Start a new Scan.

Snyk returned no matching issues

Related error: integration_empty_error

The Snyk integration responded successfully, but no issues were found that map to Bright tests.

What to do

1. Confirm that the selected Snyk project contains relevant issues.
2. Verify the integration configuration.
3. Start a new Scan after relevant data is available.

---

Bright service or engine issues

Some execution problems originate from Bright services rather than from your application configuration.

Engine ran out of memory

Related error: engine_memory_error

This can occur with very large executions or a large number of entry points.

What to do

1. Reduce the execution scope or number of entry points.
2. Split a large Scan into smaller Scans.
3. Start a new execution.

If the error continues with a normal-sized execution, contact Bright Support and provide the Scan ID, entry point count, and configuration details.

Engine or internal service error

Related errors can include:

• engine_down
• engine_internal_error
• engine_recovery_attempts_exceeded
• request_processing_failure
• unknown_error
• scan_timeout
• scan_compose_error

These errors can occur because of an unexpected Bright engine or service problem.

What to do

1. Retry the execution once.
2. If the problem happens again, contact Bright Support.

When contacting Support, include the Scan or Discovery ID and the approximate time when the error occurred. For repeated engine recovery failures, also include the target details.

---

When to contact Bright Support

Contact Bright Support when:

• The error is identified as a Bright service or internal engine issue.
• The same execution issue continues after you apply the recommended fix.
• A Scan or Discovery repeatedly fails without a clear configuration, target, authentication, or connectivity problem.
• The error message is generic and does not provide enough information to identify the cause.

Include the Scan or Discovery ID, the error message or error code, and the approximate time of the failure. If the issue involves a Repeater, target, file, or Authentication Object, include its relevant ID or configuration details.