Replies: 0
Hello Team,
One of our website went down because of the following error –
Fatal error: Uncaught RuntimeException: Error saving action: Error saving action: Table '<sitename>.wp_actionscheduler_actions' doesn't exist in /var/www/html/wordpress/<sitename>/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/migration/ActionScheduler_DBStoreMigrator.php:44 Stack trace: #0 /var/www/html/wordpress/<site_name>/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/data-stores/ActionScheduler_HybridStore.php(242): ActionScheduler_DBStoreMigrator->save_action(Object(ActionScheduler_Action), NULL) #1 /var/www/html/wordpress/<sitename>/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/ActionScheduler_ActionFactory.php(177): ActionScheduler_HybridStore->save_action(Object(ActionScheduler_Action)) #2 /var/www/html/wordpress/<sitename>/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/ActionScheduler_ActionFactory.php(84): ActionScheduler_ActionFactory->store(Object(ActionScheduler_Act in /var/www/html/wordpress/<sitename>/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/migration/ActionScheduler_DBStoreMigrator.php on line 44
As per the official documentation the issue was noticed after version 2.1.1 but in our case, the plugin was already on the higher version (2.5.1) before it was upgraded to 2.6.0 a week before. Also, the site was running fine before the upgrade and for a week after the upgrade.
Also, confirming from the DB backups, the Action Scheduler tables did not exists before the upgrade as well.
The issue was resolved after creating the Action Scheduler Tables.
I’m trying to understand why the issue was not noticed earlier before the upgrade or atleast right after the upgrade.