wpisco

Hi, thanks for the detailed reply.

I have important updates after further testing:

1. Temporary fix found:

Clearing WooCommerce transients and analytics cache resolved the recurring batch failure. After running:

• WooCommerce → Status → Tools → Clear transients (both buttons: “Clear transients” and “Clear expired transients”)
• WooCommerce → Status → Tools → Clear analytics cache

The recurring wc-admin_process_pending_orders_batch action now runs successfully and shows “No orders to process” in the logs. So a corrupted transient was almost certainly involved in the failure.

2. The “Import historical data” tool also fails:

Contrary to my initial report, the manual import tool also gets stuck. When I tried to import the last 30 days, it stopped at order 191 of 266 with the same Division by zero error in wc-admin_import_batch_orders actions. The failed action shows:
0 => 10
1 => 30
2 => false
Failed: Division by zero

The order at that position is a completed order paid via “PayPal Pay Later” (ppcp-gateway) with free shipping. Manually re-syncing this order with OrdersStatsDataStore::sync_order() works without errors, but it consistently breaks the batch importer.

3. Current state:

• Recurring batch: working again after clearing transients
• Historical import: still fails when range includes that specific order
• Store operations: working perfectly

4. System Status Report:

https://pastebin.com/GJ0tnzkx

The root cause seems to be both a regression in 10.7.0 (uncaught \DivisionByZeroError due to catch (\Exception $e) in OrdersScheduler::process_pending_batch()) AND something that corrupts the analytics transient when certain orders are processed in batch context. Changing the catch block to \Throwable would at least allow proper logging of the underlying issue.

Thanks for looking into this.

Thanks, this works!