Recurring Fatal Errors reported by WordPress

Resolved

(@florismk)

For about a week now, WordPress keeps reporting Fatal Errors from Imagify, approximately every 30-48 hours. The error details are below, but the essence seems to be that the wp_actionscheduler_actions table doesn’t exist. I’ve checked the database, and indeed it doesn’t. But it wasn’t dropped recently, so I don’t understand why this error should suddenly be thrown now?

As far as I can tell from Google, the actionscheduler tables are related to the WooCommerce Action Scheduler, and this site does not use WooCommerce at all. And I have another site that uses Imagify, doesn’t use WooCommerce, and doesn’t throw this error.

Error Details
=============
An error of type E_ERROR was caused in line 1016 of the file /mnt/web003/e2/70/511363570/htdocs/villadiodati.com/wp-content/plugins/imagify/inc/Dependencies/ActionScheduler/classes/data-stores/ActionScheduler_DBStore.php. Error message: Uncaught RuntimeException: Unable to claim actions. Database error: Table 'dbs12768442.wp_actionscheduler_actions' doesn't exist. in /mnt/web003/e2/70/511363570/htdocs/villadiodati.com/wp-content/plugins/imagify/inc/Dependencies/ActionScheduler/classes/data-stores/ActionScheduler_DBStore.php:1016
Stack trace:
#0 /mnt/web003/e2/70/511363570/htdocs/villadiodati.com/wp-content/plugins/imagify/inc/Dependencies/ActionScheduler/classes/data-stores/ActionScheduler_DBStore.php(861): ActionScheduler_DBStore->claim_actions()
#1 /mnt/web003/e2/70/511363570/htdocs/villadiodati.com/wp-content/plugins/imagify/inc/Dependencies/ActionScheduler/classes/data-stores/ActionScheduler_HybridStore.php(253): ActionScheduler_DBStore->stake_claim()
#2 /mnt/web003/e2/70/511363570/htdocs/villadiodati.com/wp-content/plugins/imagify/inc/Dependencies/ActionScheduler/classes/ActionScheduler_QueueRunner.php(179): ActionScheduler_HybridStore->stake_claim()
#3 /mnt/web003/e2/70/511363570/htdocs/villadiodati.com/wp-content/plugins/imagify/inc/Dependencies/ActionScheduler/classes/ActionScheduler_QueueRunner.php(158): ActionScheduler_QueueRunner->do_batch()
#4 /mnt/web003/e2/70/511363570/htdocs/villadiodati.com/wp-includes/class-wp-hook.php(341): ActionScheduler_QueueRunner->run()
#5 /mnt/web003/e2/70/511363570/htdocs/villadiodati.com/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters()
#6 /mnt/web003/e2/70/511363570/htdocs/villadiodati.com/wp-includes/plugin.php(570): WP_Hook->do_action()
#7 /mnt/web003/e2/70/511363570/htdocs/villadiodati.com/wp-cron.php(191): do_action_ref_array()
#8 {main}
  thrown

This topic was modified 3 months ago by Floris.

The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)

Plugin Support WPM Support
(@saranshwpm)

3 months ago

Hi @florismk,

Thank you for sharing the details and logs.

The error you’re seeing is related to the Action Scheduler library, which is used by several WordPress plugins including Imagify. However, even though the logs reference the version bundled with Imagify, the issue may not necessarily be caused by Imagify itself.

WordPress loads only one instance of the Action Scheduler—usually from the first plugin that requests it—so if other plugins (like WP Rocket and not necessarily WooCommerce) also use Action Scheduler, the actual origin of the error can be hard to pinpoint.

What you encountered seems to match a known open issue in Action Scheduler:
https://github.com/woocommerce/action-scheduler/issues/970

We’ve seen this happen occasionally in other plugins too, and in most cases, it resolves after restarting the database.

That said, if the issue reappears frequently, we recommend reviewing any overlapping scheduled tasks or reaching out to your host to monitor DB-level locks or contention.

Best regards,
The Imagify Team

Thread Starter Floris
(@florismk)

3 months ago

Thanks team! Just to clarify: Are you sure this is a similar issue? Like I said, the actionscheduler tables are not present in the WP database, and that’s the problem reported in the error. Shouldn’t those tables be present, if Imagify uses the Action Scheduler library?

Thread Starter Floris
(@florismk)

3 months ago

Additional info and question: The 2nd site that doesn’t have the actionscheduler tables also started throwing the error. Same cause reported by the trace: actionscheduler tables missing.

Since nothing changed to the database last week, there must have been some change in the plugin that triggered the error, I’d expect. Has Imagify started using the Action Scheduler, or changed its use of it, in a recent update?

I understand that the AS can be used by several plugins. However, given that the error was not thrown at all until recently, and is now thrown with Imagify as the reported source, it seems plausible to me that Imagify is indeed triggering the error.

Especially since, as I already mentioned twice, the AS tables are missing. There weren’t suddenly dropped recently. So any plugin using the AS should have been causing this error.

Thread Starter Floris
(@florismk)

3 months ago

I’ve since been able to restore the missing tables by going to the Scheduled Actions admin page. WP reported the missing tables there, and successfully attempted to restore them. I expect the error to disappear now; will report back.

Plugin Support WPM Support
(@saranshwpm)

2 months, 4 weeks ago

Hi @florismk,

Thank you for your patience, and apologies for the delay due to the holidays.

Imagify did update the AS version in a previous release back in May, and there haven’t been any recent changes that would explain this issue now. Based on that, the solution you tried should be the correct one.

If you run into any further issues or need help with anything else, please feel free to open a new thread and we’ll be glad to assist.

Best regards

Viewing 5 replies - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.