Fatal error: Invalid action status

Hello,

After doing some updates we got a fatal error coming from WooCommerce:

PHP Fatal error: Uncaught InvalidArgumentException: Invalid action status: “paused”. in /wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_wpPostStore.php:297

After doing some debugging we found out your plugin was involved just before the fatal error:

Array
(
    [0] => Array
        (
            [file] => /wp-content/plugins/woocommerce/packages/action-scheduler/functions.php
            [line] => 452
            [function] => query_actions
            [class] => ActionScheduler_HybridStore
            [type] => ->
        )

    [1] => Array
        (
            [file] => /wp-content/plugins/enhanced-e-commerce-for-woocommerce-store/enhanced-ecommerce-google-analytics.php
            [line] => 260
            [function] => as_get_scheduled_actions
        )

    [2] => Array
        (
            [file] => /wp-content/plugins/enhanced-e-commerce-for-woocommerce-store/enhanced-ecommerce-google-analytics.php
            [line] => 302
            [function] => {closure}
        )

    [3] => Array
        (
            [file] => /wp-includes/class-wp-hook.php
            [line] => 324
            [function] => conv_clear_ut_cron
        )

    [4] => Array
        (
            [file] => /wp-includes/class-wp-hook.php
            [line] => 348
            [function] => apply_filters
            [class] => WP_Hook
            [type] => ->
        )

    [5] => Array
        (
            [file] => /wp-includes/plugin.php
            [line] => 517
            [function] => do_action
            [class] => WP_Hook
            [type] => ->
        )

    [6] => Array
        (
            [file] => /wp-content/plugins/woocommerce/packages/action-scheduler/classes/abstracts/ActionScheduler.php
            [line] => 219
            [function] => do_action
        )

)

When switching back to our previous version (7.1.9) the issue was resolved. I don’t know if the issue is within the latest version (7.2.9) or a version between 7.1.9 and 7.2.9.