I see a workaround, I have requested the developers for clarification on this regard. This is actually a change in our database table structure. A permanent fix might take some time not sure about the exact deadline since we have to look into other effects of the change.
I will update you with the workaround soon probably by tomorrow.
I have checked with the developer the workaround may have some performance implications since it requires increasing the character limit of the column "filed_name" in the icl_translation table which is not a recommended way for the issue.
Since the issue requires inspecting the core aspects of the plugin, We are unable to give you a definite deadline as the issue involves adding fix without affecting any other core systems.
At this moment we can only recommend limited length for field name including repeater fields (maximum allowed field name length is 160 characters).
At this point, I've refactored the code to shorten the field length and no longer need assistance.
Since this issue resulted in a silent failure without any indication to the user that the field length was the culprit, I would recommend adding this parameter (i.e. field name length) and any other similar parameters or limitations to the ACFML documentation.
Glad you found a workaround, Thanks for the suggestion, However, the issue is not actually related only to ACF fields but related to core translation management field length. The issue is still in our developer's queue Since the fix needs to be done in core database field length which might affect performance we are considering all possibilities. We will definitely update the documentation accordingly.
