The client is experiencing slow request performance due to the large size (2.6MB) of the _wpml_jobs_not_notified option, which is set to autoload. This option is part of the translation-job notification queue and is loading on every request, significantly impacting performance.

If you\'re not using the feature of translation jobs, it\'s safe and recommended to prune the <code>_wpml_jobs_not_notified</code> option to improve performance. Before making any changes, ensure to create a full backup of your website. For a detailed explanation on managing autoload options, please visit <a href=\'https://wpml.org/forums/topic/autoload-options/\'>https://wpml.org/forums/topic/autoload-options/</a>. If this solution does not apply to your case, or if it seems outdated, we highly recommend checking related known issues at <a href=\'https://wpml.org/known-issues/\'>https://wpml.org/known-issues/</a>, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. Should you need further assistance, please open a new support ticket at <a href=\'https://wpml.org/forums/\'>WPML support forum</a>.

_wpml_jobs_not_notified is too large

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Tagged: Exception

This topic contains 2 replies, has 1 voice.

Last updated by Otto 8 months, 3 weeks ago.

Assisted by: Otto.

Author	Posts
June 4, 2025 at 3:55 pm #17107424
charlesD-31	Background of the issue: We are profiling our requests and trying to understand why some of them simply take too long. We noticed that the value of `_wpml_jobs_not_notified` option is around 2.6MB We also noticed that this option is set to `autoload`. So 2.6MB is loading in every request. Also, we noticed that the WP internal cache is frequently being asked to write the `alloptions` in the cache with this huge size. Symptoms: The `_wpml_jobs_not_notified` option is too large at 2.6MB and is set to autoload, impacting request performance. Questions: 1) what is this option used for 2) we are not using the feature of translation jobs 3) how can we disable this feature altogether? 4) is it safe to set `_wpml_jobs_not_notified` to `autoload` false?
June 5, 2025 at 6:50 am #17108697
charlesD-31	Good Morning We investigated this problem further. I hooked into wp_cache_set of WP's cache.php Indeed WPML is often trying to set: Large cache set: group='options' key='_wpml_jobs_not_notified' size=2667928 bytes Sometimes cache.php is failing: [Wed Jun 04 21:49:37.161081 2025] [proxy_fcgi:error] [pid 2722240:tid 139849545533184] [client 172.31.45.223:59288] AH01071: Got error 'PHP message: PHP Fatal error: Maximum execution time of 60 seconds exceeded in /data/www/tvm-wp/wp-includes/cache.php on line 114' I kindly refer to the questions in my first message. Thanks Reuben
June 6, 2025 at 1:26 pm #17114107
Otto WPML Supporter since 09/2015 Languages: English (English ) Spanish (Español ) Timezone: America/Argentina/Buenos_Aires (GMT-03:00)	Hello Reuben, I apologize for the delay in responding. I will take care of this ticket; the reply time will be shorter now. _wpml_jobs_not_notified is only a temporary “translation-job notification queue.” If you never assign translation jobs (locally or to a service) the option is just left-over data, and it’s perfectly safe to prune it. ❌ Please make a full website backup before proceeding ❌ Here you have a detailed explanation: https://wpml.org/forums/topic/autoload-options/ Best Regards, Otto