Since updating Jetpack to version 2.3.2, I’m getting the errors below with BackupBuyddy scheduling. These errors appear when creating or editing a scheduled job in BackupBuddy. When I deactivate Jetpack, the errors go away. When I reactivate Jetpack, the errors return. This happens on multiple sites.
Error scheduling event with WordPress. Your schedule may not work properly. Please try again. Error #3488439. Check your BackupBuddy error log for details.
Error #874784. WordPress scheduled cron event not found. See “Next Run” time in the schedules list below for problem schedule. This may be caused by a conflicting plugin deleting the schedule or manual deletion. Try editing or deleting and re-creating the schedule.
The BackupBuddy support page says,
This means the built-in WordPress function wp_schedule_event() is returning false. The only thing that can cause that is another plugin or something filtering/blocking scheduling of events. So can try deactivating/disabling all other plugins and then see if it clears it up. If it does then one of them was conflicting and can reactivate the plugins one at a time to find which one causes it again.
- The topic ‘Version 2.3.2 conflicts with BackupBuddy scheduling’ is closed to new replies.