Fatal Errors with 10.14

I am getting the following fatal errors in the debug.log using 1.0.14. The database was updated after the plugin update. [01-Feb-2026 22:35:03 UTC] PHP Fatal error: Uncaught Exception: Error on wpdb save: WordPress database error: processing the value for the following field failed: meta_value. The supplied value may be too long or contain invalid data. in /home/u258087520/domains/snappytickets.co.uk/public_html/wp-content/plugins/limb-chatbot/includes/database-strategies/class-lbaic-wpdb.php:120 Stack trace: #0 /home/u258087520/domains/snappytickets.co.uk/public_html/wp-content/plugins/limb-chatbot/includes/data-objects/class-lbaic-meta-data-object.php(203): Limb_Chatbot\Includes\Database_Strategies\WPDB->create() #1 /home/u258087520/domains/snappytickets.co.uk/public_html/wp-content/plugins/limb-chatbot/includes/data-objects/class-lbaic-chatbot-user.php(314): Limb_Chatbot\Includes\Data_Objects\Meta_Data_Object::update() #2 /home/u258087520/domains/snappytickets.co.uk/public_html/wp-content/plugins/limb-chatbot/includes/services/class-lbaic-user-manager.php(445): Limb_Chatbot\Includes\Data_Objects\Chatbot_User->update_meta() #3 /home/u258087520/domains/snappytickets.co.uk/public_html/wp-content/plugins/limb-chatbot/includes/services/class-lbaic-user-manager.php(204): Limb_Chatbot\Includes\Services\User_Manager->store_device_info() #4 /home/u258087520/domains/snappytickets.co.uk/public_html/wp-content/plugins/limb-chatbot/includes/services/class-lbaic-user-manager.php(67): Limb_Chatbot\Includes\Services\User_Manager->define_current_user() #5 /home/u258087520/domains/snappytickets.co.uk/public_html/wp-content/plugins/limb-chatbot/includes/api/v1/controllers/class-lbaic-rest-controller.php(95): Limb_Chatbot\Includes\Services\User_Manager->get_current_user() #6 /home/u258087520/domains/snappytickets.co.uk/public_html/wp-content/plugins/limb-chatbot/includes/api/v1/controllers/class-lbaic-chatbots-controller.php(282): Limb_Chatbot\Includes\Api\V1\Controllers\Rest_Controller->permission_callback() #7 /home/u258087520/domains/snappytickets.co.uk/public_html/wp-includes/rest-api/class-wp-rest-server.php(1259): Limb_Chatbot\Includes\Api\V1\Controllers\Chatbots_Controller->get_items_permissions_check() #8 /home/u258087520/domains/snappytickets.co.uk/public_html/wp-includes/rest-api/class-wp-rest-server.php(1125): WP_REST_Server->respond_to_request() #9 /home/u258087520/domains/snappytickets.co.uk/public_html/wp-includes/rest-api/class-wp-rest-server.php(439): WP_REST_Server->dispatch() #10 /home/u258087520/domains/snappytickets.co.uk/public_html/wp-includes/rest-api.php(467): WP_REST_Server->serve_request() #11 /home/u258087520/domains/snappytickets.co.uk/public_html/wp-includes/class-wp-hook.php(341): rest_api_loaded() #12 /home/u258087520/domains/snappytickets.co.uk/public_html/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters() #13 /home/u258087520/domains/snappytickets.co.uk/public_html/wp-includes/plugin.php(570): WP_Hook->do_action() #14 /home/u258087520/domains/snappytickets.co.uk/public_html/wp-includes/class-wp.php(418): do_action_ref_array() #15 /home/u258087520/domains/snappytickets.co.uk/public_html/wp-includes/class-wp.php(821): WP->parse_request() #16 /home/u258087520/domains/snappytickets.co.uk/public_html/wp-includes/functions.php(1343): WP->main() #17 /home/u258087520/domains/snappytickets.co.uk/public_html/wp-blog-header.php(16): wp() #18 /home/u258087520/domains/snappytickets.co.uk/public_html/index.php(17): require('/home/u25808752...') #19 {main} thrown in /home/u258087520/domains/snappytickets.co.uk/public_html/wp-content/plugins/limb-chatbot/includes/database-strategies/class-lbaic-wpdb.php on line 120 Can I downgrade the plugin now the database has been updated? Hi @joncon62 Thanks for the report. Since the database was updated in 1.0.14, we’d like to review things first before recommending a downgrade, just to avoid any potential issues. We’ll contact you directly by email, investigate the errors, and either fix this with you or release a follow-up update. We’ll keep you updated today. Hi @joncon62 Please update the plugin to v1.0.15 (latest) . After updating, go to Limb and click “Migrate” in the migration popup that appears. This will complete the fix. If you face anything else, let us know. Thanks @raffiyeghiazaryan that’s fixed it.