Hi there,
I use the plugin WP Crontrol to view scheduled Cron events and check for any issues.
After installing it I go to WordPress Menu >> Tools >> Cron Events and do a search.
Using the keyword ‘updraft’ I filter the events and check they’re scheduled correctly.
The cron event for updraft_backup_database should definitely be present in events.
If it is not please go to your Settings and re-save your Database backup schedule.
You should check the Cron Events again to make sure the new event entry is there.
Best regards,
Nick
Thread Starter
VAR
(@varrie29)
Thanks for the suggestion.
I installed the plugin and can confirm that the updraft_backup_database is listed in Cron Events: https://prnt.sc/0VYhYKj_hR2i
So the scheduled backup probably ran in the past through that cron event but failed. Can we enable logging so I can trigger manual run of the cron event from that WP Crontrol plugin and see some information on why it fails?
Thanks!
Thread Starter
VAR
(@varrie29)
Or I have PHP logging already enabled via some plugin. Will it reflect something there if I manually run the scheduled cron event updraft_backup_database via WP Crontrol plugin and it fails?
Not sure how to go about it since manual backups (full website backup) work just fine.
Hi there,
Thanks for the updates.
Unfortunately there wouldn’t be any log output regarding a failed cron event in this case.
If the event isn’t being triggered it suggests a problem with the WordPress scheduler itself.
There are a number of reasons the scheduler can fail, they’re listed in an article linked here:
https://teamupdraft.com/documentation/updraftplus/topics/general/troubleshooting/how-to-fix-the-wordpress-missed-schedule-error/
You can consider the issues described but ultimately you may need help from your hosting.
They can more easily investigate the problem and possibly set up a new cron job for you.
Best regards,
Nick
Thread Starter
VAR
(@varrie29)
Thanks for your response but that doesn’t really help. The web host cannot help as it is just this scheduled process that is not working. As I have mentioned, I have several scheduled processes and they’re all working fine (e.g. scheduled automatic product stock status update, abandoned cart sequence, etc.).
The ones in your help page are very generic troubleshooting that would otherwise affect several other scheduled processes. I have already looked into them but they’re not the cause of it. Moreover, several other scheduled processes I have are more complex and would likely to fail first.
Can you please advise a more helpful/reliable way to troubleshoot scheduled backup processes that are failing? I need to check at which point it fails. Your response assumes the cron did not run but why would it do that if all other cron events did run? Or if the assumption is incorrect and the cron did actually ran, I need to see why it aborted the backup job.
Thanks!
Hi there,
Thank you, I’m happy to help.
The difficulty is we’re not able to access your site and investigate ourselves.
The WordPress forum rules specifically forbid us from asking for any details.
The scheduler is not part of the plugin, it resides within you site installation.
Only the hosting has access to this, that’s why they are in a position to help.
So while we can offer generic troubleshooting tips, we can’t actually access.
You’ve described a scenario where a scheduled event didn’t run as intended.
Based on this I’ve suggested the scheduling mechanism needs to be checked.
And as I’ve mentioned, there is no way we can perform such a check for you.
In short, I’ve advised the most helpful/reliable method to troubleshoot this.
The advice is based on practical constraints over which we have no control.
If the backup did run and then abort you would have a log file for the backup.
If this is the case please share the log file using a sharing service like Pastebin.
If there is no log file it would indicate the backup event was not triggered.
Which would lead us back to my original suggestion, ask hosting to assist.
Best regards,
Nick
It’s been a while since we heard from you. I am closing the ticket but please feel free to reach out if you have any further concerns.
