Common Errors and Troubleshooting Scan Errors

This page is intended for all users running scans and need help resolving errors that occur during the scan process. While most scans complete without issue, you may occasionally encounter Scan Errors. These occur when the crawler is unable to successfully reach or process a specific URL in your list.

Identifying Errors

If issues were detected during a scan, an alert badge will appear directly below the scan timestamp indicating the number of errors (e.g., "80 Errors During Scan").

Viewing Error Details

To investigate why specific pages failed:

• Click the Errors During Scan badge.
• A Scan Errors modal will appear, listing every URL that failed.
• Each entry includes the specific URL and a "View error details" dropdown.
• Review the technical log (e.g., "Execution context was destroyed") to determine if the issue is a broken redirect, a server timeout, or a page that requires authentication.

Scan Timeouts

Very large audits can take several hours, because Equalify scans the pages in an audit one after another. A scan is only given up on when no page has reported back for a full hour. When that happens:

• A Scan Timed Out notice appears above the blockers chart. It says how many of the audit's pages were never scanned.
• Each page that was never scanned appears in the Errors During Scan list with a Not Scanned (Timeout) label, so you can see exactly which URLs are missing from the report. (If more than 500 pages are affected, the first 500 are listed and the notice gives the full count.)
• Results for every page that was scanned are kept and shown as usual.

A timeout usually means the scanning queue stalled, not that your pages are broken. Re-run the scan. If the same pages keep failing, check whether they can be reached from outside your network.