WP Cerber errors found in Error_log

While chasing down a problem (that I hope is unrelated to WP Cerber), I found more than a few entries in my error_log file related to WP Cerber. I don’t think this is causing any problems, but wanted to report it anyway. Here are a few of the entries, just the most recent:

[09-Feb-2024 17:57:06 UTC] Cron unschedule event error for hook: cerber_bg_launcher, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:“crb_five”,“args”:,“interval”:300}
[21-Feb-2024 04:35:40 UTC] Cron reschedule event error for hook: cerber_bg_launcher, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:“crb_five”,“args”:,“interval”:300}
[26-Feb-2024 22:32:45 UTC] Cron reschedule event error for hook: wp_fastest_cache_Preload, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:“everyfiveminute”,“args”:,“interval”:300}
[04-Mar-2024 23:12:17 UTC] Cron reschedule event error for hook: cerber_hourly_2, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:“hourly”,“args”:,“interval”:3600}
[05-Mar-2024 03:45:42 UTC] Cron reschedule event error for hook: cerber_bg_launcher, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:“crb_five”,“args”:,“interval”:300}

I see issues related specifically to saving WordPress scheduled tasks. They are not related to WP Cerber. However, this anomaly could potentially lead to more serious problems later on.