Skip to content

A scan stopped or takes long

Why a scan can stop before it finishes, and what to do about it.

A scan runs on WordPress’s own scheduler, WP-Cron, which runs when someone visits the site. On a quiet site, or when WP-Cron is disabled, a scan can wait or stop. A scan that stops shows Scan stopped before finishing on the Dashboard, with the reason. The most common ones:

  • WordPress did not start this scan within 24 hours. Check that the WP Rooster plugin is active and that WP-Cron runs on this site, then scan again.
  • WordPress started collecting files and did not continue within 1 hour. Check that WP-Cron runs on this site, then scan again.
  • WordPress did not send the requested files. Check that WP Rooster is connected, then scan again.
  • The scan stopped making progress. Start another scan to try again.

Fix what the reason names, then select Scan again. Starting a scan yourself also runs again any code analysis that could not finish.

Code analysis takes longer than the scan itself. The first one on a large site can take several hours. That is normal, and the scan is complete only when it has finished.