Reply to – Sync delay 1 time?

In response to the earlier question (see below) from @amoses0612.
First, apologies, I was too slow with my reply and meanwhile the topic is closed to new replies. Hence this new topic..

Reply:
Indeed strange! This must have something to do with the way WordPress triggers the storage of data.

Is it conceivable that you fire a field in a frontend form twice? For example Gravity Forms (and probably other plugins too) have the option to add a hidden field to a form, and populate it with any dynamic field value already present in the form. Perhaps if you trigger the form to store field X twice it might fire in SyncFields and do proper syncing?
Just a long shot…

Hi, thanks a lot for such a useful plugin.
According to my test,

User A changed and saved the field X in the frontend profile form, A’s field X wasn’t synced to field Y.

User B changed and saved the field X in the frontend profile form, A’s field X was synced to field Y. B’s field X wasn’t synced to field Y.

User C changed and saved the field X in the frontend profile form, B’s field X was synced to field Y. C’s field X wasn’t synced to field Y.

User C made no change but saved the form again, C’s field X was synced to field Y.

So strange.

I am using MariaDB Galera Cluster and InnoDB. Is it the possible reason causing the result above? Is it possible to trigger the sync twice every time data is changed?