Just adding additional info here: It seems that once the scan finally kicks off, it completes in a reasonable time. The problem is in kicking off the scan. Once one hits “Scan Now”, we’re greeted with an “Initiating scan” type of message that lasts and lasts and lasts. Once that goes away, function resumes.
Are you now waiting on wp-cron?
Or heartbeat?
Are you now sending our blog information back to your mothership without asking, and analyzing it and waiting for a response before proceeding?
What’s the delay?
Hi @thefitrv,
The latest AIOS updates for scanner tasks use an AJAX-based polling system.
Previously, a scan would start and you would only be notified once it had completed. Now, the browser periodically checks the progress of the scan and updates the interface as the task progresses.
The scanner is not cron-based. The scan task is stored in the database, and the Heartbeat API is used to track its progress and relay status updates back to the browser.
No blog content or site information is transmitted. The AJAX requests are used solely to check the status and progress of the scanner task running on your site.
I will create an internal ticket for the issue you have raised so that we can investigate it further.
Regards
This makes sense. I use Heartbeat Control by WP Rocket. I’ve basically disabled the heartbeat from everywhere. Perhaps that is what is delaying UI updates in my case.
But the scan *does* eventually initiate and complete (usually). Is there a backup trigger mechanism? Or am I just eventually getting updates because of a default 60 second heartbeat or something?
Hi @thefitrv,
Let me check internally whether it is possible to disable the heartbeat for this scanner in AIOS. I don’t think it is likely, as there doesn’t appear to be a setting for this.
The HEARTBEAT_INTERVAL is set to 10 seconds, not 60 seconds.
The mechanism here works by retrieving the status of the scan task from the database at regular intervals.
I need to look into this in more detail to understand exactly how it works for scheduled scans. As the scan progresses, its state is stored in the database, with statuses such as: started, initialised, starting, fetching, scanning, comparing, saving, and completed.
Regards
