‘wf_scan_monitor’ wp-cron event schedule

  • Resolved David Adams

    (@tictag)


    1 year, 10 months ago

    I note that your wf_scan_monitor wp-cron hook runs at wf_scan_monitor_interval schedule i.e. every 1 minute.

    Is such a rapid schedule really required?

    I have disabled the wp-cron scheduler in favour of a 30 minute OS-initiated cron(tab) job to run the scheduler, which means that wf_scan_minitor is only running every 30 minutes instead of every minute.

    Will this cause any problems?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Hi @tictag, thanks for your message.

    wf_scan_monitor?usually only appears during a Wordfence scan as it just watches a running scan to ensure it completes, and it does not need to be rescheduled in your list of WP Cron jobs when it ends. That will explain why it looks so frequently, but once the scan is over it will normally stop running.

    Your 30-minute cron schedule shouldn’t cause any issues with the scan monitor aside from delaying retries if there?were?a failure during a running scan. We’d normally recommend running cron jobs at least every 5 minutes.

    We do have a development case open for occasions it doesn’t stop, as you may have been witnessing here. If you can send us a full scan log, it may help narrow down the cause.

    If you check Wordfence > Scan > Email Activity Log, you can send it to wftest @ wordfence . com. Just let me know when you’ve sent it so I can take a look for it in our inbox.

    Thanks,
    Peter.

    Thread Starter David Adams

    (@tictag)

    Email with screenshots and activity logs provided.

    David.

    Plugin Support wfpeter

    (@wfpeter)

    Many thanks @tictag, these have been forwarded to the team to assist with the development work in this area.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘‘wf_scan_monitor’ wp-cron event schedule’ is closed to new replies.