Why my scheduled backups don't fire?

The reason varies depending on the server and WordPress configurations. We don't have sufficient access to your resources to figure out exactly what's the cause. So, you can check the following:

  • Look for a line like this in your wp-config.php file (which is found in the root directory of your WordPress installation), and remove it (or change true to false, making sure there are no quote marks around false):

    define('DISABLE_WP_CRON', true);

  • Is your website in maintenance mode? This disables all kind of scheduled tasks – so turn it off first.

  • WordPress' scheduler relies on the site having visitors. No visitors means that WordPress doesn't run, and therefore can't hand over to the scheduled task. If your site is in development, and you schedule a backup run for a time when all the developers are asleep, then that may be the cause for the scheduled tasks not running.

  • Some web hosting providers (one big example: Heart Internet) purposefully (though for no good reason) disable the "loop-back" connects that allows WordPress to run its scheduler. If loopback connections are not working (whether deliberately disabled or not), you can try to use the alternative scheduling system of WordPress – instructions here: https://codex.wordpress.org/Editing_wp-config.php#Alternative_Cron. The instructions amount to one thing: add a line anywhere in the middle of your wp-config.php file as follows (don't add it too late in the file, or it will take no effect):

    define('ALTERNATE_WP_CRON', true);


Back to search