• This plugin works great. Order lookup time went from 10+ seconds to 1-2 seconds

    I am seeing an error in my php logs

    [08-Apr-2026 10:23:29 UTC] WordPress database error Deadlock found when trying to get lock; try restarting transaction for query
    INSERT INTO wp_actionscheduler_actions ( hook, status, scheduled_date_gmt, scheduled_date_local, schedule, group_id, priority, args )
    SELECT ‘fast_woo_order_lookup_textdex_action’, ‘pending’, ‘2026-04-08 10:23:29’, ‘2026-04-08 10:23:29’, ‘O:28:\”ActionScheduler_NullSchedule\”:0:{}’, 19, 10, ‘[]’ FROM DUAL
    WHERE (
    SELECT action_id FROM wp_actionscheduler_actions
    WHERE status IN ( ‘pending’, ‘in-progress’ )
    AND hook = ‘fast_woo_order_lookup_textdex_action’
    AND group_id = 19
    LIMIT 1 ) IS NULL made by do_action(‘admin_init’), WP_Hook->do_action, WP_Hook->apply_filters, Fast_Woo_Order_Lookup{closure}, Fast_Woo_Order_Lookup\FastWooOrderLookup::getInstance, Fast_Woo_Order_Lookup\FastWooOrderLookup->__construct, Fast_Woo_Order_Lookup\Textdex->load_textdex, Fast_Woo_Order_Lookup\Textdex->schedule_batch, as_enqueue_async_action, ActionScheduler_ActionFactory->create, ActionScheduler_ActionFactory->store_unique_action, ActionScheduler_DBStore->save_unique_action, ActionScheduler_DBStore->save_action_to_db

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

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author OllieJones

    (@olliejones)

    Thanks for the bug report. The dreaded ActionScheduler deadlock problem. I’m investigating now.

    Please let me know if this is a rare occurrence or if it happens all the time.

    Plugin Author OllieJones

    (@olliejones)

    A few observations.

    1. If your ActionScheduler‘s actions table has many actions in it, that can make this deadlock more likely. Visit Tools -> Scheduled Actions to see what’s going on there. Failed and canceled actions don’t get cleaned out automatically. You can use wp-cli to bulk delete failed actions like this:
      wp action-scheduler clean --status=failed,canceled
    2. This error, if it only occurs rarely, is benign. The action scheduler tries again.
    3. It is more likely to happen on sites with concurrent action scheduler workers.
    4. I’m investigating whether it’s possible to remediate this in the plugin. I don’t want to simply suppress concurrent workers, because that might disrupt operations.

    I hope this helps. Again, any more information you have on the failure will help me.

    Thread Starter strictlymedicinal

    (@strictlymedicinal)

    Somewhat rare. It has happened 28 times in 17 days.

    The deadlock also seems to happen occasionally during checkout process unrelated to this plugin.

    I’m getting two failed actions everyday – wc_sc_aggregate_daily_time

    Thanks!

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

You must be logged in to reply to this topic.