• Resolved Robert

    (@rsterry48)


    Since we updated to WP 6.1.1 we are getting this cron event appearing as an error in our PHP Error Log on the Dashboard [we are using Error Log Monitor to display in the Dashboard]:
    Cron reschedule event error for hook: action_scheduler_run_queue, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:”every_minute”,”args”:[“WP Cron”],”interval”:60}

    This has never appeared in the PHP Error Log before. The cron event is set to run every 1 minute but the error only appears in the Log every few days. It doesn’t appear in the Log if I run it manually using WP Crontrol.

    Any idea why this is happening? I can set Error Log Monitor to ignore the error so it doesn’t appear in the Dashboard, but is this a good idea?
    Many thanks
    Robert

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author John Blackbourn

    (@johnbillion)

    WordPress Core Developer

    Thanks for the report. This is unrelated to WP Crontrol and is most likely an error that has been occurring prior to WordPress 6.1, except that in 6.1 extra error reporting was added so previously unseen errors such as this are now logged.

    Here’s where the new logging was added: https://core.trac.www.ads-software.com/ticket/56048

    Here’s a similar report to yours after the change: https://core.trac.www.ads-software.com/ticket/57271

    You might want to report the issue to Action Scheduler too but it’s likely not specific to that plugin.

    Thread Starter Robert

    (@rsterry48)

    Thank you so very much John. A really helpful reply. So based on your reply, I assume we can set the PHP Errors being displayed by the plugin Error Log Monitor [and are cluttering up our Dashboard] to ‘Ignore’ but leave the errors in the error log itself for reference if needed?

    Plugin Author John Blackbourn

    (@johnbillion)

    WordPress Core Developer

    Yep that sounds sensible.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘PHP Error-action_scheduler_run_queue’ is closed to new replies.