[wp-trac] [WordPress Trac] #57271: Cron unschedule / reschedule event errors

WordPress Trac noreply at wordpress.org
Wed Feb 22 17:54:23 UTC 2023


#57271: Cron unschedule / reschedule event errors
----------------------------------------+------------------------------
 Reporter:  domainsupport               |       Owner:  audrasjb
     Type:  defect (bug)                |      Status:  assigned
 Priority:  normal                      |   Milestone:  Awaiting Review
Component:  Cron API                    |     Version:  6.0
 Severity:  normal                      |  Resolution:
 Keywords:  has-patch needs-unit-tests  |     Focuses:
----------------------------------------+------------------------------

Comment (by courageous999):

 Replying to [comment:17 j3gaming]:
 > Replying to [comment:16 domainsupport]:
 > > I've not seen the errors appear in our logs for some time now
 (although I'm under no illusion that the issue has resolved itself).
 However in all instances that we have seen this issue, it was with PHP 7.4
 so @AndyHenderson I don't think that your PHP update to v8.1 was relevant.
 > >
 > > Oliver
 >
 > I'm still experiencing this and it's deleting my cron jobs. Are you
 saying the fix is to update PHP? Is there any code changes for this coming
 up in the next version of wordpress?
 We're currently running WordPres 6.1.1 and we updated to PHP 8.1 a little
 over a month ago and I'm still seeing errors like this in the logs about
 once a month (some of these are from plugins like Wordfence it seems):

 {{{
 [17-Feb-2023 15:24:47 UTC] 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}
 [08-Feb-2023 21:36:00 UTC] Cron reschedule event error for hook:
 wf_scan_monitor, Error code: could_not_set, Error message: The cron event
 list could not be saved., Data:
 {"schedule":"wf_scan_monitor_interval","args":[],"interval":60}
 }}}
 So I can confirm that updating to PHP 8.1 will not resolve this issue.

 Furthermore, I don't think that WordPress is officially ready for PHP 8.1
 yet as our logs are filled with errors from the "wp-includes" folder in
 WordPress.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/57271#comment:18>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list