Hi Woodmart Support Team,
I’m experiencing a critical error on my WooCommerce website that appears to originate from the Woodmart theme’s Floating Blocks module.
The Error:
[02-Feb-2026 15:06:21 UTC] RedisException: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE. in /wp-content/object-cache.php:2173
Stack Trace (pointing to Woodmart):
The stack trace clearly shows the error originates from:
themes/woodmart/inc/modules/floating-blocks/class-manager.php(506): set_transient()
themes/woodmart/inc/modules/floating-blocks/class-manager.php(218): get_all_conditions()
themes/woodmart/inc/modules/floating-blocks/class-frontend.php(169): get_current_ids()
What I’ve already done to troubleshoot:
Disabled Object Caching (Redis) on my hosting (Elementor Hosting)
Disabled all plugins except WooCommerce
Contacted my hosting provider – they confirmed the issue is not on their infrastructure side
Generated new WooCommerce API keys
The impact:
This error is causing conflicts with my ERP system (Semplisio) that synchronizes products via WooCommerce REST API. The synchronization was working perfectly before and has now stopped.
My environment:
Hosting: Elementor Hosting
Theme: Woodmart (latest version)
WordPress: Latest version
WooCommerce: Latest version
My questions:
Is there a known conflict between the Floating Blocks module and Redis/Object Caching?
Is there a way to disable or optimize the set_transient() calls in the Floating Blocks module?
Are there any recommended settings to prevent this issue?
I would really appreciate your assistance as this is affecting my production e-commerce store.
Thank you in advance.
Best regards,
.
