Which system of record takes precedence during bidirectional synchronization conflicts?

Jira Align utilizes a bidirectional synchronization engine to map strategic themes and programs to Jira Software epics and stories. This process relies on specific field mapping configurations and a defined connection user to maintain data integrity across both platforms.

When simultaneous updates occur on the same field in both Jira Align and Jira Software, the system must resolve the conflict to prevent data inconsistency or synchronization loops. While connector settings allow for the definition of a system of record, the behavior during rapid, overlapping updates remains a critical configuration point for maintaining a reliable audit trail.

Does the synchronization engine prioritize the most recent timestamp regardless of the system of record setting, or does the defined system of record always override the opposing value? In what scenario would a synchronization loop be triggered by these conflict resolution rules?