Cronjobs with WordPress 5.5 and last run of cronjob

Hi,

Thanks for your message. The plugin hasn’t actually been tested for WordPress 5.5 yet but the core functionality that the plugin uses hasn’t changed, so I can’t see a concern with this. This plugin is essentially just a user interface for WordPress’s native task scheduler.

Currently, the only way you can tell if a cronjob is running is if the next run time keeps incrementing. If that isn’t changing or is stuck at a date in the past, then the cron task won’t be running.

Hope this helps! Chris.

Hi Chris,

Thank you very much for your fast response!

In my case, the time stopped incrementing. The time there stopped incrementing when I changed the PHP version to 7.4 and updated WordPress to 5.5. But I am not 100% sure if the two changes are linked to the cronjob stopping to run.

*Even if I add the task newly (I just did it now). For example, I have added it to run every minute – but the first run after I do this is already in the past. It tells me “28. August 2020 14:29”

Do you have a tip where I could look further, to make it run again?

• This reply was modified 4 years, 3 months ago by giebraltar.

Hey, I’m having the same issue, time for all cronjobs stopped incrementing.

You need to configure an actual server side cron task to make sure your schedules are firing. Please refer to the docs.

If you have a cron schedule setup, double check it and make sure it’s actually triggering.

Hi Chris

Nice plugin thanks – I am in the same situation as Daniel – Since I upgraded to WP 5.5 and php 7.4 a few weeks ago my Updraft Plus backups have not completed, they run approx 1/3 of the way and then stop with no error messages. I realise that it can’t be due to your plugin as once the cron job is fired your plugin is not going to halt it, but based on your knowledge of cron jobs is there anything else you could suggest (I have the cron job that you suggest running every minute) or could my host maybe have done something?

Thanks
Pete