• Hello,

    I get this error: “[13-Jul-2023 07:44:18 UTC] Failed to cancel cron scheduling event for hook: wordfence_start_scheduled_scan, error code: could_not_set, error message: Scheduled event list could not be saved., data: { “schedule”:false,”args”:[1689215401]}”

    Is it possible to hide it or fix it?

    and these ones:

    “[10-Jul-2023 10:42:47 UTC] Failed to cancel cron scheduling event for hook: wordfence_start_scheduled_scan, error code: could_not_set, error message: Scheduled event list could not be saved., data: { “schedule”:false,”args”:[1688956200]}
    [10-Jul-2023 11:05:25 UTC] Cron reschedule event failed for hook: rocket_rucss_pending_jobs, error code: invalid_schedule, error message: Event schedule does not exist., data: {“schedule”:”rocket_rucss_pending_jobs” ,”args”:[],”range”:60}
    [10-Jul-2023 11:05:57 UTC] Error rescheduling cron event for hook: action_scheduler_run_queue, error code: invalid_schedule, error message: Event schedule does not exist., data: {“schedule”:”every_minute” ,”args”:[“WP Cron”],”range”:60}
    [10-Jul-2023 11:06:11 UTC] Error rescheduling cron event for hook: action_scheduler_run_queue, error code: invalid_schedule, error message: Event schedule does not exist., data: {“schedule”:”every_minute” ,”args”:[“WP Cron”],”range”:60}”

    Thanks!

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

    (@wfpeter)

    Hi @madalingaiu, thanks for the detailed logs.

    Are these from your server log files or an external tool/plugin? I say this because we sometimes utilize WordPress’ $wpdb->suppress_errors(true); function in situations we know an error may occur. This might sound counter-intuitive but there’s no fixed amount of resources we know Wordfence will use on each customers’ server. Therefore, some non-critical situations where it’s more expensive on resources to retry or check for the presence of a file/record, we simply choose to fail silently and continue.

    As the messages are regarding the scheduling and cancelling of cron tasks, do you see any permissions errors or overdue cron jobs on your Wordfence > Tools > Diagnostics page? If more than just Wordfence cron jobs (they’re the ones prefixed with “wordfence_” or “wf_”) are displayed as overdue, you may need to look at things like caching settings that could be stopping them.

    Let me know what you find out,
    Peter.

    Thread Starter madalingaiu

    (@madalingaiu)

    Hello,

    I found the errors here: server log files

    We use the wp rocket plugin.

    Is it possible to be a problem with ur plugin and wp rocket? or our server is low in resourse to avoid those errors?

    If it helps u, i can offer acces in our wp admin.

    Thanks!

    Plugin Support wfpeter

    (@wfpeter)

    Hi @madalingaiu,

    I think it might be best to see if any configuration issues might be linked to the cron errors, as I haven’t seen them combined with WPRocket before to speculate on whether there’s certainly a link between Wordfence and a conflict.

    Please can you send a site diagnostic to us at wftest @ wordfence . com directly using the link at the top of the Wordfence > Tools > Diagnostics page? Click on “Send Report by Email”. Please add your forum username where indicated and respond here after you have sent it.

    NOTE: It should look as follows – Screenshot of Tools > Diagnostic > Send by Email

    Thanks again,
    Peter.

    I’m getting these errors as well with Wordfense:

    [20-Jul-2023 07:07:05 UTC] Cron unschedule event error for hook: wordfence_start_scheduled_scan, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:false,”args”:[1689832800]}

    [23-Jul-2023 07:07:05 UTC] Cron unschedule event error for hook: wordfence_start_scheduled_scan, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:false,”args”:[1690092000]}

    [26-Jul-2023 07:07:05 UTC] Cron unschedule event error for hook: wordfence_start_scheduled_scan, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:false,”args”:[1690351200]}

    [29-Jul-2023 07:07:06 UTC] Cron unschedule event error for hook: wordfence_start_scheduled_scan, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:false,”args”:[1690610400]}

    What is causing them?

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