Skip to content

A scan does not start

Why a scan is refused or keeps waiting, and what to do.

When a site is disconnected, paused, switched off or not reporting, its scan button is disabled and the notice at the top of the page says why. Without the Manual scans permission there is no scan button.

When the scan shows Waiting for WordPress, WP Rooster waits for the site to pick it up. The site picks it up when WP Rooster’s request to start it gets through, or at its next check-in. WordPress usually starts a scan within 10 minutes. A scan that waits longer usually means a firewall refuses the request, or WP-Cron does not run on the site.

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.