Cron unschedule event error

  • Resolved Mike Witt

    (@mike80222)


    9 months ago

    Hi,

    Is this anything to be concerned about:

    Cron unschedule event error for hook: wordfence_processAttackData, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:false,”args”:[]}

    When I look in: Wordfence > Tools > Diagnostics > Cron Jobs I don’t see wordfence_processAttackData anywhere, and I don’t see any such task running with wp_crontrol. For whatever that’s worth.

    I’m just asking because this is the first time I’ve ever seen a Cron error with WF. I’m still running WF 7.11.5 of that matters.

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

    (@wfpeter)

    Hi @mike80222,

    This is a log message they added to wp-cron around 1-2 years ago, but isn’t related to a PHP error or a sign that cron is broken in some way.

    WordPress can sometimes start two copies of wp-cron to run the same jobs, triggered by multiple hits on the site starting close together. As wp-cron’s locking is imperfect, the jobs may run twice. When one finishes, it updates the list of cron jobs, and then when the other finishes, it’s unable to make the same update, because it’s already done. There was previously no log to report it, but now it’s intentionally logged in WordPress.

    Thanks,
    Peter.

    Thread Starter Mike Witt

    (@mike80222)

    Thanks @wfpeter. That is quite interesting and explains a number of Cron messages I never understood before!

    • This reply was modified 9 months ago by Mike Witt.
Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Cron unschedule event error’ is closed to new replies.