[Escalated to 2nd Tier] New Glossary not updating on ATE.

Hi Carlos,

As requested, here are the specific errors and notices currently appearing in our debug log:

1. WPML String Translation Warnings
We are seeing multiple Undefined array key warnings for the following keys: "job_id", "automatic", "editor", "translation_service", and "review_status".
Location: /wp-content/plugins/wpml-string-translation/StringTranslation/Infrastructure/Translation/Query/FindTranslationDetailsQuery.php (Lines 73 and 76)
2. ACF Textdomain Notice
Error: PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the acf domain was triggered too early.

I am also attaching the debug.log file for your scrutiny.
Please let me know how we should proceed to resolve these.

debug.log:
hidden link

Hi Carlos,
Thank you for the update.
As requested, I have created a video recording showing the setup and the behavior on our end: hidden link

For your reference, here are the specific page URLs featured in the video:
Glossary Test CSV:
German: hidden link
English: hidden link
Glossary Test (not featured in the video, but the glossary term is displayed):
German: hidden link
English: hidden link

I understand that this issue might not replicate in a clean sandbox environment. However, because these specific PHP warnings and textdomain notices are often tied to environment configurations and existing database strings, could you please try replicating or investigating this directly on our staging site?

You already have administrative access to our staging environment, where these errors are consistently generating in the debug log.
Please let me know if you need me to re-send the login credentials or if your 2nd-tier specialists can jump straight into the staging site to investigate further.

Hi Paola,

​Thank you for taking over this ticket and looking into our issue.

​Regarding the "Preserve related Translation Memory entries" setting mentioned in your message, I wanted to clarify that we actually ensured this option was disabled during our import.

​If you take a look at the video recording between the 1:18 and 1:22 timestamps, you can see that "Replace existing terms" is checked, but "Preserve related Translation Memory entries" is explicitly left unchecked. (By the way, it looks like the video link you included in your reply accidentally points back to this same recording I sent over, so I wasn't able to view your new screencast!)

Because the translations are still failing to update even with that setting disabled, the underlying issue seems to be caused by something else. Since you already have administrative access to our staging environment, could you or the 2nd-tier specialists try replicating the import directly on the staging site to see why it isn't overwriting as expected?

​Looking forward to your findings.

Hi Paola,

I hope you are doing well.

I am just checking in to see if the second-tier specialists have had a chance to look into this issue or if there are any updates since it was escalated last Wednesday (June 17).

We are looking forward to any insights or workarounds they might recommend so we can move forward with our staging environment.

Thank you for your continued help!