Plugin Support
qtwrk
(@qtwrk)
please enable WP_DEBUG_LOG , there should be few more lines before this error message, that carries more important traceback info
Hello,
In debug.log there is nothing related with this database error
Plugin Support
qtwrk
(@qtwrk)
do you have reliable method to reproduce and trigger the error message ?
I think errors occur when automatic processes of LiteSpeed or ActionScheduler access to DB.
For instance:
[27-Aug-2026 23:23:14 UTC] WordPress database error Commands out of sync; you can’t run this command now for query SELECT option_value FROM wp_options WHERE option_name = ‘wc_pending_batch_processes’ LIMIT 1 made by shutdown_action_hook, do_action(‘shutdown’), WP_Hook->do_action, WP_Hook->apply_filters, Automattic\WooCommerce\Internal\BatchProcessing\BatchProcessingController->Automattic\WooCommerce\Internal\BatchProcessing{closure}, Automattic\WooCommerce\Internal\BatchProcessing\BatchProcessingController->remove_or_retry_failed_processors, Automattic\WooCommerce\Internal\BatchProcessing\BatchProcessingController->get_enqueued_processors, get_option
[27-Aug-2026 23:23:14 UTC] WordPress database error Commands out of sync; you can’t run this command now for query SELECT option_value FROM wp_options WHERE option_name = ‘litespeed.optimax._summary’ LIMIT 1 made by LiteSpeed\Core->send_headers_force, LiteSpeed\Root::cls, LiteSpeed\Optimax->__construct, LiteSpeed\Root::get_summary, LiteSpeed\Root::get_option, get_option
[27-Aug-2026 23:23:23 UTC] WordPress database error Commands out of sync; you can’t run this command now for query SELECT option_value FROM wp_options WHERE option_name = ‘litespeed.optimax._summary’ LIMIT 1 made by LiteSpeed\Core->send_headers_force, LiteSpeed\Root::cls, LiteSpeed\Optimax->__construct, LiteSpeed\Root::get_summary, LiteSpeed\Root::get_option, get_option
Plugin Support
qtwrk
(@qtwrk)
from the log you posted, I think there is some plugin incorrectly manipulating the database connection or query , and then in turn , our plugin or woocommerce were doing some DB query and happen to hit that issue