Fatal error in WPML Translation Manager – translation entry not found although record exists

Sun	Mon	Tue	Wed	Thu	Fri	Sat
-	7:00 – 12:00	7:00 – 12:00	7:00 – 12:00	7:00 – 12:00	7:00 – 12:00	-
-	12:00 – 15:00	12:00 – 15:00	12:00 – 15:00	12:00 – 15:00	12:00 – 15:00	-

Supporter timezone: Europe/Vienna (GMT+02:00)

This topic contains 0 reply, has 1 voice.

Last updated by sebastianK-50 1 month, 3 weeks ago.

Assisted by: Lucas Vidal de Andrade.

Author	Posts
March 16, 2026 at 9:44 am #17899261
sebastianK-50	Hello, we are experiencing a recurring fatal error related to WPML when editing or autosaving a post. The error occurs during the WordPress heartbeat autosave process. Error message: Uncaught InvalidArgumentException: No translation entry found for query: trid = 54603 AND language_code = en File: /wp-content/plugins/sitepress-multilingual-cms/classes/records/class-wpml-tm-icl-translations.php:193 Stack trace shows the error is triggered during: heartbeat_autosave → wpml_tm_save_post → WPML_TM_ICL_Translations Environment: WordPress: 6.9.4 WPML Multilingual CMS: 4.8.6 PHP: 8.2.30 Custom post type: news Translation group: TRID: 54603 Translations in the database: language post ID de 32349 en 32357 cs 32356 fr 32358 sk 32359 All translation records exist correctly in the wp_icl_translations table. Background: The website was migrated previously, so we suspect that some WPML translation relations or caches might have become inconsistent after the migration. Questions: -Why does WPML throw this exception even though the translation record exists in the database? -Is this related to the translation manager cache or autosave process? -Are there recommended troubleshooting or database repair steps to permanently prevent this? -Could this be a known issue with WPML Translation Manager during autosave? We already verified that the translation entries exist and that the posts can now be saved again without error. We also ran the WPML troubleshooting tools. Any guidance on preventing this from happening again would be appreciated. Best regards

Author

Posts

March 16, 2026 at 9:44 am #17899261

sebastianK-50

Hello,

we are experiencing a recurring fatal error related to WPML when editing or autosaving a post. The error occurs during the WordPress heartbeat autosave process.

Error message:
Uncaught InvalidArgumentException: No translation entry found for query:
trid = 54603 AND language_code = en

File:
/wp-content/plugins/sitepress-multilingual-cms/classes/records/class-wpml-tm-icl-translations.php:193

Stack trace shows the error is triggered during:
heartbeat_autosave → wpml_tm_save_post → WPML_TM_ICL_Translations

Environment:
WordPress: 6.9.4
WPML Multilingual CMS: 4.8.6
PHP: 8.2.30
Custom post type: news

Translation group:
TRID: 54603

Translations in the database:
language post ID
de 32349
en 32357
cs 32356
fr 32358
sk 32359

All translation records exist correctly in the wp_icl_translations table.

Background:
The website was migrated previously, so we suspect that some WPML translation relations or caches might have become inconsistent after the migration.

Questions:
-Why does WPML throw this exception even though the translation record exists in the database?
-Is this related to the translation manager cache or autosave process?
-Are there recommended troubleshooting or database repair steps to permanently prevent this?
-Could this be a known issue with WPML Translation Manager during autosave?

We already verified that the translation entries exist and that the posts can now be saved again without error. We also ran the WPML troubleshooting tools. Any guidance on preventing this from happening again would be appreciated.

Best regards