Fatal error in scheduler

  • saens

    (@saens)


    5 years ago

    Hi,
    I’ve updated my staging to 4.0 (based on a fresh copy off of live). I’m getting fatal errors when I import existing data into the new Analytics”

    2020-03-11T09:58:16+00:00 CRITICAL Uncaught InvalidArgumentException: Onge?dentificeerde actie 3 in /mnt/web419/b0/82/59534982/htdocs/WordPress_03/wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_wpPostStore.php:495
Stack trace:
#0 /mnt/web419/b0/82/59534982/htdocs/WordPress_03/wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_wpPostStore.php(482): ActionScheduler_wpPostStore->get_date_gmt('3')
#1 /mnt/web419/b0/82/59534982/htdocs/WordPress_03/wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_HybridStore.php(274): ActionScheduler_wpPostStore->get_date('3')
#2 /mnt/web419/b0/82/59534982/htdocs/WordPress_03/wp-content/plugins/woocommerce/packages/action-scheduler/classes/ActionScheduler_wcSystemStatus.php(78): ActionScheduler_HybridStore->get_date('3')
#3 /mnt/web419/b0/82/59534982/htdocs/WordPress_03/wp-content/plugins/woocommerce/packages/action-scheduler/classes/ActionScheduler_wcSystemStatus.php(52): ActionSchedu in /mnt/web419/b0/82/59534982/htdocs/WordPress_03/wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_wpPostStore.php op de lijn 495

2020-03-11T10:00:08+00:00 CRITICAL Uncaught InvalidArgumentException: Onge?dentificeerde actie 3 in /mnt/web419/b0/82/59534982/htdocs/WordPress_03/wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_wpPostStore.php:495
Stack trace:
#0 /mnt/web419/b0/82/59534982/htdocs/WordPress_03/wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_wpPostStore.php(482): ActionScheduler_wpPostStore->get_date_gmt('3')
#1 /mnt/web419/b0/82/59534982/htdocs/WordPress_03/wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_HybridStore.php(274): ActionScheduler_wpPostStore->get_date('3')
#2 /mnt/web419/b0/82/59534982/htdocs/WordPress_03/wp-content/plugins/woocommerce/packages/action-scheduler/classes/ActionScheduler_wcSystemStatus.php(78): ActionScheduler_HybridStore->get_date('3')
#3 /mnt/web419/b0/82/59534982/htdocs/WordPress_03/wp-content/plugins/woocommerce/packages/action-scheduler/classes/ActionScheduler_wcSystemStatus.php(52): ActionSchedu in /mnt/web419/b0/82/59534982/htdocs/WordPress_03/wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_wpPostStore.php op de lijn 495

2020-03-11T10:00:23+00:00 CRITICAL Uncaught InvalidArgumentException: Ongeldig actie ID. Geen status gevonden. in /mnt/web419/b0/82/59534982/htdocs/WordPress_03/wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_wpPostStore.php:740
Stack trace:
#0 /mnt/web419/b0/82/59534982/htdocs/WordPress_03/wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_HybridStore.php(326): ActionScheduler_wpPostStore->get_status('3')
#1 /mnt/web419/b0/82/59534982/htdocs/WordPress_03/wp-content/plugins/woocommerce/packages/action-scheduler/classes/ActionScheduler_ListTable.php(533): ActionScheduler_HybridStore->get_status('3')
#2 /mnt/web419/b0/82/59534982/htdocs/WordPress_03/wp-content/plugins/woocommerce/packages/action-scheduler/classes/abstracts/ActionScheduler_Abstract_ListTable.php(659): ActionScheduler_ListTable->prepare_items()
#3 /mnt/web419/b0/82/59534982/htdocs/WordPress_03/wp-content/plugins/woocommerce/packages/action-scheduler/classes/ActionScheduler_AdminView.php(94): Act in /mnt/web419/b0/82/59534982/htdocs/WordPress_03/wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_wpPostStore.php op de lijn 740

2020-03-11T10:02:33+00:00 CRITICAL Uncaught InvalidArgumentException: Onge?dentificeerde actie 3 in /mnt/web419/b0/82/59534982/htdocs/WordPress_03/wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_wpPostStore.php:495
Stack trace:
#0 /mnt/web419/b0/82/59534982/htdocs/WordPress_03/wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_wpPostStore.php(482): ActionScheduler_wpPostStore->get_date_gmt('3')
#1 /mnt/web419/b0/82/59534982/htdocs/WordPress_03/wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_HybridStore.php(274): ActionScheduler_wpPostStore->get_date('3')
#2 /mnt/web419/b0/82/59534982/htdocs/WordPress_03/wp-content/plugins/woocommerce/packages/action-scheduler/classes/ActionScheduler_wcSystemStatus.php(78): ActionScheduler_HybridStore->get_date('3')
#3 /mnt/web419/b0/82/59534982/htdocs/WordPress_03/wp-content/plugins/woocommerce/packages/action-scheduler/classes/ActionScheduler_wcSystemStatus.php(52): ActionSchedu in /mnt/web419/b0/82/59534982/htdocs/WordPress_03/wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_wpPostStore.php op de lijn 495

2020-03-11T10:03:57+00:00 CRITICAL Uncaught InvalidArgumentException: Onge?dentificeerde actie 177 in /mnt/web419/b0/82/59534982/htdocs/WordPress_03/wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_wpPostStore.php:457
Stack trace:
#0 /mnt/web419/b0/82/59534982/htdocs/WordPress_03/wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_HybridStore.php(248): ActionScheduler_wpPostStore->cancel_action('177')
#1 /mnt/web419/b0/82/59534982/htdocs/WordPress_03/wp-content/plugins/woocommerce/packages/action-scheduler/classes/abstracts/ActionScheduler_Store.php(290): ActionScheduler_HybridStore->cancel_action('177')
#2 /mnt/web419/b0/82/59534982/htdocs/WordPress_03/wp-content/plugins/woocommerce/packages/action-scheduler/classes/abstracts/ActionScheduler_Store.php(275): ActionScheduler_Store->bulk_cancel_actions(Array)
#3 /mnt/web419/b0/82/59534982/htdocs/WordPress_03/wp-content/plugins/woocommerce/packages/woocommerce-admin/src/Schedulers/SchedulerTraits.php(356): Actio in /mnt/web419/b0/82/59534982/htdocs/WordPress_03/wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_wpPostStore.php op de lijn 457

2020-03-11T10:04:10+00:00 CRITICAL Uncaught InvalidArgumentException: Onge?dentificeerde actie 3 in /mnt/web419/b0/82/59534982/htdocs/WordPress_03/wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_wpPostStore.php:495
Stack trace:
#0 /mnt/web419/b0/82/59534982/htdocs/WordPress_03/wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_wpPostStore.php(482): ActionScheduler_wpPostStore->get_date_gmt('3')
#1 /mnt/web419/b0/82/59534982/htdocs/WordPress_03/wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_HybridStore.php(274): ActionScheduler_wpPostStore->get_date('3')
#2 /mnt/web419/b0/82/59534982/htdocs/WordPress_03/wp-content/plugins/woocommerce/packages/action-scheduler/classes/ActionScheduler_wcSystemStatus.php(78): ActionScheduler_HybridStore->get_date('3')
#3 /mnt/web419/b0/82/59534982/htdocs/WordPress_03/wp-content/plugins/woocommerce/packages/action-scheduler/classes/ActionScheduler_wcSystemStatus.php(52): ActionSchedu in /mnt/web419/b0/82/59534982/htdocs/WordPress_03/wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_wpPostStore.php op de lijn 495
Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Contributor Peter Fabian

    (@peterfabian1000)

    Hi @saens , thanks for reporting the error to us and sorry to hear you’re having problems.

    The errors above seem to indicate they were triggered from the System status report when fetching the oldest and most recent scheduled actions. Maybe this happened while the migration of actions was in progress? Can you please elaborate on the order of operations when you upgraded your staging environment?

    Have you tried to disable other plugins while doing the upgrade to rule out potential plugin conflict?

    Thread Starter saens

    (@saens)

    I have disabled almost all plugins. Active are: Disable Emails, Kadence WooCommerce Email Designer, Limit Login Attempts, Really Simple SSL, WooCommerce.

    What I did was update woocommerce to 4.0
    Then navigate to Analytics -> Settings -> Import Historical Data
    And then import all historical data. It stays at 0 with a spinning symbol next to it.

    The error message is copied from the System status.

    When I check the tab Scheduled Actions next to System status there is a message saying there’s been a critial error (I’m guessing the one linked above)

    Are these two different issues then, maybe?

    Thread Starter saens

    (@saens)

    I also have Subscriptions installed, but inactive on staging (it is updated to latest version)

    Thread Starter saens

    (@saens)

    When I go to Tools -> Scheduled actions
    It shows that a migration of scheduled actions is active. However it’s been ~5-7hrs since I updated to 4.0
    There’s less than 10 scheduled actions (subscriptions) active on live

    Thread Starter saens

    (@saens)

    I have enabled debug on my staging. When I try to load the scheduled actions I get:

    [11-Mar-2020 16:47:54 UTC] PHP Fatal error:  Uncaught InvalidArgumentException: Invalid action ID. No status found. in /mnt/web419/b0/82/59534982/htdocs/WordPress_03/wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_wpPostStore.php:740
Stack trace:
#0 /mnt/web419/b0/82/59534982/htdocs/WordPress_03/wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_HybridStore.php(326): ActionScheduler_wpPostStore->get_status('3')
#1 /mnt/web419/b0/82/59534982/htdocs/WordPress_03/wp-content/plugins/woocommerce/packages/action-scheduler/classes/ActionScheduler_ListTable.php(533): ActionScheduler_HybridStore->get_status('3')
#2 /mnt/web419/b0/82/59534982/htdocs/WordPress_03/wp-content/plugins/woocommerce/packages/action-scheduler/classes/abstracts/ActionScheduler_Abstract_ListTable.php(659): ActionScheduler_ListTable->prepare_items()
#3 /mnt/web419/b0/82/59534982/htdocs/WordPress_03/wp-content/plugins/woocommerce/packages/action-scheduler/classes/ActionScheduler_AdminView.php(94): ActionSc in /mnt/web419/b0/82/59534982/htdocs/WordPress_03/wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_wpPostStore.php on line 740
    • This reply was modified 5 years ago by saens.

    I’m getting the exact same fatal error on my live instance!

    WordPress databasefout: [Table 'sparkpiercing_woolive20.wpyx_actionscheduler_logs' doesn't exist]
SHOW FULL COLUMNS FROM <code>wpyx_actionscheduler_logs</code>

WordPress databasefout: [Table 'sparkpiercing_woolive20.wpyx_actionscheduler_logs' doesn't exist]
SHOW FULL COLUMNS FROM <code>wpyx_actionscheduler_logs</code>

WordPress databasefout: [Table 'sparkpiercing_woolive20.wpyx_actionscheduler_logs' doesn't exist]
SHOW FULL COLUMNS FROM <code>wpyx_actionscheduler_logs</code>

WordPress databasefout: [Table 'sparkpiercing_woolive20.wpyx_actionscheduler_logs' doesn't exist]
SHOW FULL COLUMNS FROM <code>wpyx_actionscheduler_logs</code>

    This is strange, table is pressend in db

    beka47

    (@beka47)

    me too, SIMILAR after trying to update from 3.9.3 to 4.0
    schedular tables are present.

    2020-03-19T20:24:08+00:00 CRITICAL Uncaught InvalidArgumentException: Nicht identifizierte Aktion 1 
in /home/.../wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_wpPostStore.php:495
Stack trace:
#0 /home/.../wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_wpPostStore.php(482): ActionScheduler_wpPostStore->get_date_gmt('1')
#1 /home/.../wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_HybridStore.php(274): ActionScheduler_wpPostStore->get_date('1')
#2 /home/.../wp-content/plugins/woocommerce/packages/action-scheduler/classes/ActionScheduler_wcSystemStatus.php(78): ActionScheduler_HybridStore->get_date('1')
#3 /home/.../wp-content/plugins/woocommerce/packages/action-scheduler/classes/ActionScheduler_wcSystemStatus.php(52): ActionSche in /home/.../plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_wpPostStore.php in Zeile 495
    • This reply was modified 5 years ago by beka47.

    Same error for me :

    [06-Apr-2020 14:15:10 UTC] PHP Fatal error:  Uncaught InvalidArgumentException: Action 11 non identifiée in /.../wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_wpPostStore.php:495
Stack trace:
#0 /.../wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_wpPostStore.php(482): ActionScheduler_wpPostStore->get_date_gmt('11')
#1 /.../wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_HybridStore.php(274): ActionScheduler_wpPostStore->get_date('11')
#2 /.../wp-content/plugins/woocommerce/packages/action-scheduler/classes/ActionScheduler_wcSystemStatus.php(78): ActionScheduler_HybridStore->get_date('11')
#3 /.../wp-content/plugins/woocommerce/packages/action-scheduler/classes/ActionScheduler_wcSystemStatus.php(52): ActionScheduler_wcSystemStatus->get_action_status_date('complete', 'oldest')
#4 /... in /home/.../wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_wpPostStore.php on line 495
    • This reply was modified 4 years, 11 months ago by benoitfouc.

    Anyone got this fixed, got the same issue.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Fatal error in scheduler’ is closed to new replies.