The background update process could be required based on your chosen translation option for the field groups.
We'll need to discuss with our development team if there's an option to cancel the update process, but we will need to check which option you have for translating the field group.
Please let us know if you chose the Same fields across languages, Different fields across languages, or the Expert mode.
Hi there,
Thank you for the reply. I’ve selected expert mode and then copy option as I don’t want these fields to be translated. Also selected this in the translation rules.
Currently, there isn't an option to cancel the update process. It is running in the background so you can leave it as it is and it will be done automatically.
The process is run when the translation preference of a custom field is changed which may imply that a translation needs updating (e.g. if a field was previously set to No translate and is changed to Translate or Copy). The batch process simply updates the translation status of affected posts (posts that use this custom field).
So what you see and experience here is kind of expected, but since you probably have many post/custom fields it takes time to run this process. The batch processes require time to complete and are browser-based, not server-based. So if you (wp users) navigate away before the processes are complete they will keep re-starting.
If the process is stuck for too long please check to debug log for any issues.
How is the update process on your site going? You can try to open a browser tab, go to ACF > Edit field group > Resave the field group settings and keep the browser available until the update process finish.
It would take time to finish the update process on your site. If the process is stuck for too long please check to debug log for any issues. Please follow the documentation to get the debug log https://wpml.org/documentation/support/debugging-wpml/
The solution is quite straightforward. Go to your fields in the ACF plugin and save them again without changing anything there. It will trigger the update on the wpml.
