[Resolved] WPML 4.8.4 update interface freezing after

Thank you for the explanation and suggestions.

At the moment, we are manually checking a large number of translations and custom fields to ensure nothing was lost or desynced. This is a very time-consuming process and requires significant effort from both our content team and developers.

To be honest, we’re quite disappointed that this issue requires manual intervention and database-level actions to mitigate the problem. The update from WPML 4.7.6 to 4.8.6 has resulted in a situation where normal editorial work became almost impossible, and resolving it now takes a substantial amount of time.

Ideally, an update between stable WPML versions should not require manual database manipulation or background task cleanup in order to restore basic usability. This kind of recovery process is risky and not something we would expect to handle manually after a plugin update.

We understand the potential causes you mentioned (background tasks, REST API, WPEngine Governor), but we would appreciate clearer guidance on:

how to safely verify that all translations and custom fields are fully synchronized after removing background tasks, and

whether a more reliable or automated recovery approach exists (or is planned) to avoid manual checks in such cases.