[Fatal] PHP Fatal error: Uncaught RuntimeException: Unable to release actions from claim id 0 | ActionScheduler_DBStore.php:1042

[nigeljamesstevenson]

Prerequisites

• I have carried out troubleshooting steps and I believe I have found a bug.
• I have searched for similar bugs in both open and closed issues and cannot find a duplicate.

Describe the bug

We observed the following fatal error in relation to WooCommerce 9.3.3

Link to code

Stack trace:

PHP Fatal error:  Uncaught RuntimeException: Unable to release actions from claim id 0. in /../plugins/woocommerce/9.3.3/packages/action-scheduler/classes/data-stores/ActionScheduler_DBStore.php:1042
Stack trace:
#0 /../plugins/woocommerce/9.3.3/packages/action-scheduler/classes/ActionScheduler_FatalErrorMonitor.php(52): ActionScheduler_DBStore->release_claim(Object(ActionScheduler_ActionClaim))
woocommerce/woocommerce#1 /../core/6.6.2/wp-includes/class-wp-hook.php(324): ActionScheduler_FatalErrorMonitor->handle_unexpected_shutdown('')
woocommerce/woocommerce#2 /../core/6.6.2/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array)
woocommerce/woocommerce#3 /../core/6.6.2/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
woocommerce/woocommerce#4 /../core/6.6.2/wp-includes/load.php(1280): do_action('shutdown')
woocommerce/woocommerce#5 [internal function]: shutdown_action_hook()
woocommerce/woocommerce#6 {main}
  thrown in /../plugins/woocommerce/9.3.3/packages/action-scheduler/classes/data-stores/ActionScheduler_DBStore.php on line 1042

Expected behavior

No fatal errors when attempting to release actions

Actual behavior

Fatal errors when attempting to release actions

Steps to reproduce

We don't have steps to reproduce, but observed 1312 instances of this problem on Fri Oct 11, 1200 UTC to 2359 UTC on one site.

Also observed 383 instances of this error on another site but it referenced line 956 of the same ActionScheduler_DBStore.php so likely a different installation/version

Hopefully, someone can dig in and apply a defensive check if appropriate. - To be updated after investigation.

WordPress Environment

N/A

Isolating the problem

• I have deactivated other plugins and confirmed this bug occurs when only WooCommerce plugin is active.
• This bug happens with a default WordPress theme active, or Storefront.
• I can reproduce this bug consistently using the steps above.

[albarin]

May be related to woocommerce/woocommerce#52157