Title: fatal-errors Last modified: June 14, 2025 --- # fatal-errors * Resolved [trevellfr](https://wordpress.org/support/users/trevellfr/) * (@trevellfr) * [11 months, 4 weeks ago](https://wordpress.org/support/topic/fatal-errors-107/) * Hi ! * Since some days I have this kind of error in the woocomerce log : * ```wp-block-code 2025-06-14T00:04:14+00:00 Critique Uncaught InvalidArgumentException: Unidentified action 1716464: we were unable to mark this action as having failed. It may may have been deleted by another process. in /home/pabr8108/mydomain.fr/wp-content/plugins/imagify/inc/Dependencies/ActionScheduler/classes/data-stores/ActionScheduler_DBStore.php:1185 Contexte supplémentaire{ "error": { "type": 1, "file": "/home/pabr8108/mydomain.fr/wp-content/plugins/imagify/inc/Dependencies/ActionScheduler/classes/data-stores/ActionScheduler_DBStore.php", "line": 1185 }, "remote-logging": true, "backtrace": [ "", "#0 /home/pabr8108/mydomain.fr/wp-content/plugins/imagify/inc/Dependencies/ActionScheduler/classes/ActionScheduler_QueueCleaner.php(225): ActionScheduler_DBStore->mark_failure()", "#1 /home/pabr8108/mydomain.fr/wp-content/plugins/imagify/inc/Dependencies/ActionScheduler/classes/ActionScheduler_QueueCleaner.php(238): ActionScheduler_QueueCleaner->mark_failures()", "#2 /home/pabr8108/mydomain.fr/wp-content/plugins/imagify/inc/Dependencies/ActionScheduler/classes/abstracts/ActionScheduler_Abstract_QueueRunner.php(241): ActionScheduler_QueueCleaner->clean()", "#3 /home/pabr8108/mydomain.fr/wp-content/plugins/imagify/inc/Dependencies/ActionScheduler/classes/ActionScheduler_QueueRunner.php(152): ActionScheduler_Abstract_QueueRunner->run_cleanup()", "#4 /home/pabr8108/mydomain.fr/wp-includes/class-wp-hook.php(324): ActionScheduler_QueueRunner->run()", "#5 /home/pabr8108/mydomain.fr/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()", "#6 /home/pabr8108/mydomain.fr/wp-includes/plugin.php(565): WP_Hook->do_action()", "#7 /home/pabr8108/mydomain.fr/wp-cron.php(191): do_action_ref_array()", "#8 {main}", "thrown" ]}2025-06-14T01:30:09+00:00 Critique Uncaught InvalidArgumentException: Unidentified action 1716645: we were unable to mark this action as having failed. It may may have been deleted by another process. in /home/pabr8108/mydomain.fr/wp-content/plugins/imagify/inc/Dependencies/ActionScheduler/classes/data-stores/ActionScheduler_DBStore.php:1185 Contexte supplémentaire{ "error": { "type": 1, "file": "/home/pabr8108/mydomain.fr/wp-content/plugins/imagify/inc/Dependencies/ActionScheduler/classes/data-stores/ActionScheduler_DBStore.php", "line": 1185 }, "remote-logging": true, "backtrace": [ "", "#0 /home/pabr8108/mydomain.fr/wp-content/plugins/imagify/inc/Dependencies/ActionScheduler/classes/ActionScheduler_QueueCleaner.php(225): ActionScheduler_DBStore->mark_failure()", "#1 /home/pabr8108/mydomain.fr/wp-content/plugins/imagify/inc/Dependencies/ActionScheduler/classes/ActionScheduler_QueueCleaner.php(238): ActionScheduler_QueueCleaner->mark_failures()", "#2 /home/pabr8108/mydomain.fr/wp-content/plugins/imagify/inc/Dependencies/ActionScheduler/classes/abstracts/ActionScheduler_Abstract_QueueRunner.php(241): ActionScheduler_QueueCleaner->clean()", "#3 /home/pabr8108/mydomain.fr/wp-content/plugins/imagify/inc/Dependencies/ActionScheduler/classes/ActionScheduler_QueueRunner.php(152): ActionScheduler_Abstract_QueueRunner->run_cleanup()", "#4 /home/pabr8108/mydomain.fr/wp-includes/class-wp-hook.php(324): ActionScheduler_QueueRunner->run()", "#5 /home/pabr8108/mydomain.fr/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()", "#6 /home/pabr8108/mydomain.fr/wp-includes/plugin.php(565): WP_Hook->do_action()", "#7 /home/pabr8108/mydomain.fr/wp-cron.php(191): do_action_ref_array()", "#8 {main}", "thrown" ]}2025-06-14T10:41:42+00:00 Critique Uncaught InvalidArgumentException: Unidentified action 1717715: we were unable to mark this action as having failed. It may may have been deleted by another process. in /home/pabr8108/mydomain.fr/wp-content/plugins/imagify/inc/Dependencies/ActionScheduler/classes/data-stores/ActionScheduler_DBStore.php:1185 Contexte supplémentaire{ "error": { "type": 1, "file": "/home/pabr8108/mydomain.fr/wp-content/plugins/imagify/inc/Dependencies/ActionScheduler/classes/data-stores/ActionScheduler_DBStore.php", "line": 1185 }, "remote-logging": true, "backtrace": [ "", "#0 /home/pabr8108/mydomain.fr/wp-content/plugins/imagify/inc/Dependencies/ActionScheduler/classes/ActionScheduler_QueueCleaner.php(225): ActionScheduler_DBStore->mark_failure()", "#1 /home/pabr8108/mydomain.fr/wp-content/plugins/imagify/inc/Dependencies/ActionScheduler/classes/ActionScheduler_QueueCleaner.php(238): ActionScheduler_QueueCleaner->mark_failures()", "#2 /home/pabr8108/mydomain.fr/wp-content/plugins/imagify/inc/Dependencies/ActionScheduler/classes/abstracts/ActionScheduler_Abstract_QueueRunner.php(241): ActionScheduler_QueueCleaner->clean()", "#3 /home/pabr8108/mydomain.fr/wp-content/plugins/wp-rocket/inc/Engine/Common/Queue/RUCSSQueueRunner.php(176): ActionScheduler_Abstract_QueueRunner->run_cleanup()", "#4 /home/pabr8108/mydomain.fr/wp-includes/class-wp-hook.php(324): WP_Rocket\Engine\Common\Queue\RUCSSQueueRunner->run()", "#5 /home/pabr8108/mydomain.fr/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()", "#6 /home/pabr8108/mydomain.fr/wp-includes/plugin.php(565): WP_Hook->do_action()", "#7 /home/pabr8108/mydomain.fr/wp-cron.php(191): do_action_ref_array()", "#8 {main}", "thrown" ]}2025-06-14T12:47:05+00:00 Critique Uncaught InvalidArgumentException: Unidentified action 1717897: we were unable to mark this action as having failed. It may may have been deleted by another process. in /home/pabr8108/mydomain.fr/wp-content/plugins/imagify/inc/Dependencies/ActionScheduler/classes/data-stores/ActionScheduler_DBStore.php:1185 Contexte supplémentaire{ "error": { "type": 1, "file": "/home/pabr8108/mydomain.fr/wp-content/plugins/imagify/inc/Dependencies/ActionScheduler/classes/data-stores/ActionScheduler_DBStore.php", "line": 1185 }, "remote-logging": true, "backtrace": [ "", "#0 /home/pabr8108/mydomain.fr/wp-content/plugins/imagify/inc/Dependencies/ActionScheduler/classes/ActionScheduler_QueueCleaner.php(225): ActionScheduler_DBStore->mark_failure()", "#1 /home/pabr8108/mydomain.fr/wp-content/plugins/imagify/inc/Dependencies/ActionScheduler/classes/ActionScheduler_QueueCleaner.php(238): ActionScheduler_QueueCleaner->mark_failures()", "#2 /home/pabr8108/mydomain.fr/wp-content/plugins/imagify/inc/Dependencies/ActionScheduler/classes/abstracts/ActionScheduler_Abstract_QueueRunner.php(241): ActionScheduler_QueueCleaner->clean()", "#3 /home/pabr8108/mydomain.fr/wp-content/plugins/imagify/inc/Dependencies/ActionScheduler/classes/ActionScheduler_QueueRunner.php(152): ActionScheduler_Abstract_QueueRunner->run_cleanup()", "#4 /home/pabr8108/mydomain.fr/wp-includes/class-wp-hook.php(324): ActionScheduler_QueueRunner->run()", "#5 /home/pabr8108/mydomain.fr/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()", "#6 /home/pabr8108/mydomain.fr/wp-includes/plugin.php(565): WP_Hook->do_action()", "#7 /home/pabr8108/mydomain.fr/wp-cron.php(191): do_action_ref_array()", "#8 {main}", "thrown" ]}2025-06-14T14:49:24+00:00 Critique Uncaught InvalidArgumentException: Unidentified action 1717985: we were unable to mark this action as having failed. It may may have been deleted by another process. in /home/pabr8108/mydomain.fr/wp-content/plugins/imagify/inc/Dependencies/ActionScheduler/classes/data-stores/ActionScheduler_DBStore.php:1185 Contexte supplémentaire{ "error": { "type": 1, "file": "/home/pabr8108/mydomain.fr/wp-content/plugins/imagify/inc/Dependencies/ActionScheduler/classes/data-stores/ActionScheduler_DBStore.php", "line": 1185 }, "remote-logging": true, "backtrace": [ "", "#0 /home/pabr8108/mydomain.fr/wp-content/plugins/imagify/inc/Dependencies/ActionScheduler/classes/ActionScheduler_QueueCleaner.php(225): ActionScheduler_DBStore->mark_failure()", "#1 /home/pabr8108/mydomain.fr/wp-content/plugins/imagify/inc/Dependencies/ActionScheduler/classes/ActionScheduler_QueueCleaner.php(238): ActionScheduler_QueueCleaner->mark_failures()", "#2 /home/pabr8108/mydomain.fr/wp-content/plugins/imagify/inc/Dependencies/ActionScheduler/classes/abstracts/ActionScheduler_Abstract_QueueRunner.php(241): ActionScheduler_QueueCleaner->clean()", "#3 /home/pabr8108/mydomain.fr/wp-content/plugins/wp-rocket/inc/Engine/Common/Queue/RUCSSQueueRunner.php(176): ActionScheduler_Abstract_QueueRunner->run_cleanup()", "#4 /home/pabr8108/mydomain.fr/wp-includes/class-wp-hook.php(324): WP_Rocket\Engine\Common\Queue\RUCSSQueueRunner->run()", "#5 /home/pabr8108/mydomain.fr/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()", "#6 /home/pabr8108/mydomain.fr/wp-includes/plugin.php(565): WP_Hook->do_action()", "#7 /home/pabr8108/mydomain.fr/wp-cron.php(191): do_action_ref_array()", "#8 {main}", "thrown" ]} ``` * Maybe you need some informations : * WC Version: 9.9.3 * WP Version: 6.8.1 * Imagify: par Imagify Image Optimizer – Optimize Images & Convert WebP & Avif – 2.2.6 * Action Scheduler : * Complete: 37 061 Oldest: 2025-06-14 05:38:22 +0200Newest: 2025-06-14 16:49:24 +0200 * Failed: 2 594 Oldest: 2024-04-27 04:08:50 +0200Newest: 2025-06-11 04:01:58 +0200 * In-progress: 1 Oldest: –Newest: – * Pending: 45 Oldest: 2025-06-14 16:25:13 +0200Newest: 2025-06-21 05:04:48 +0200 Viewing 2 replies - 1 through 2 (of 2 total) * Plugin Support [imagifysupport](https://wordpress.org/support/users/imagifysupport/) * (@imagifysupport) * [11 months, 3 weeks ago](https://wordpress.org/support/topic/fatal-errors-107/#post-18514422) * Hi, * Thanks for sharing the detailed logs. * This seems to be the same issue as reported by another user here: * 👉 [https://wordpress.org/support/topic/actionscheduler-deadlock-possibly-caused-from-imagify-update/](https://wordpress.org/support/topic/actionscheduler-deadlock-possibly-caused-from-imagify-update/) * Can you please confirm if your case matches that? * Just to clarify, this isn’t directly caused by Imagify. The error comes from the Action Scheduler library, which is used by multiple plugins like WooCommerce, WP Rocket, and Imagify—but only one instance is loaded by WordPress at a time. So while the log points to Imagify’s path, the root cause could be from any plugin using Action Scheduler. * In the other thread, the user fixed it by restarting the database and adjusting some server-level resources. You might want to try that as well. * Plugin Support [imagifysupport](https://wordpress.org/support/users/imagifysupport/) * (@imagifysupport) * [11 months, 3 weeks ago](https://wordpress.org/support/topic/fatal-errors-107/#post-18519697) * Hello, As we didn’t hear from you, I’m marking this as resolved.Feel free to follow up or open a new thread if you need any assistance.Best Regards, Viewing 2 replies - 1 through 2 (of 2 total) The topic ‘fatal-errors’ is closed to new replies. * ![](https://ps.w.org/imagify/assets/icon-256x256.gif?rev=3452959) * [Imagify: Optimize Images for Top Speed (Compress & Convert to WebP/AVIF)](https://wordpress.org/plugins/imagify/) * [Frequently Asked Questions](https://wordpress.org/plugins/imagify/#faq) * [Support Threads](https://wordpress.org/support/plugin/imagify/) * [Active Topics](https://wordpress.org/support/plugin/imagify/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/imagify/unresolved/) * [Reviews](https://wordpress.org/support/plugin/imagify/reviews/) * 2 replies * 2 participants * Last reply from: [imagifysupport](https://wordpress.org/support/users/imagifysupport/) * Last activity: [11 months, 3 weeks ago](https://wordpress.org/support/topic/fatal-errors-107/#post-18519697) * Status: resolved