Sync & Conflicts

This page covers the sync behavior of Computtite cloud mode workspaces. Understanding it helps you diagnose issues and reason about how conflicts are resolved when multiple people edit simultaneously.

Sync Status States

The sync status indicator in the bottom status bar shows the current sync state:

• idle: No sync activity. The app is between automatic cycles.
• syncing: A sync cycle is in progress.
• up-to-date: The last sync completed successfully with no pending changes.
• offline: No internet connectivity. Changes are queued and will sync when connectivity is restored.
• error: The last sync attempt failed. Hover over the indicator to see the error message.

How Sync Works

Every change you make (create, update, delete) is saved locally first, then queued to be sent to the cloud. The pending changes count in the status bar reflects how many local changes are waiting. Every 10 seconds, Computtite automatically sends pending changes and checks for new changes from other members.

Conflict Resolution in Detail

When two members update the same record simultaneously, the most recent change wins. The other version's data is not recoverable through the UI, but both operations are recorded in the audit log (accessible to Admins and Owners).

In practice, true conflicts are rare in most ITAM environments because different people typically edit different assets. The risk of collision is highest in scenarios where many Admins rapidly edit the same configuration records (e.g., rapidly updating the same asset type's field definitions). For these scenarios, coordinate through team communication to avoid conflicts.

Manual Sync Trigger

You can force an immediate sync at any time by clicking the sync icon in the status bar or going to Settings → Sync → Sync now. This is useful after making a batch of changes that you want to push immediately rather than waiting for the next 10-second cycle.