Component instance property synchronization between Figma desktop and web clients

Figma maintains component definitions via a cloud-based version graph to ensure consistency across collaborative environments. However, the desktop client utilizes cached snapshots of these definitions to maintain performance and offline accessibility.

When a component is updated via the web client while a desktop client is offline or operating on a stale cache, there is uncertainty regarding how the system resolves property overrides upon reconnection. Specifically, it is unclear if the server-side commit takes precedence or if the local cached state triggers a conflict in instance properties.

Does Figma provide a mechanism to verify which specific component version the desktop client is currently rendering relative to the server? How does the synchronization process handle property mismatches between a cached local instance and a newly published cloud version?