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

[WordPress Trac]

#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 domainsupport):

 Having not had these errors in the logs for a while, they have made a re-
 appearance ...

 {{{
 [16-Dec-2022 06:48:13 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}
 [16-Dec-2022 06:48:13 UTC] Cron unschedule 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}
 [16-Dec-2022 06:48:15 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}
 }}}

 I think this is significant because I thought that the update of core
 itself could have been a cause but there hasn't been an update for a long
 time. Furthermore, the schedule for this hook is 1 minute and it's a
 custom schedule / hook. This means that whatever the cause is, it is
 independent of core / custom schedule and independent of core / custom
 hook.

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