Whether a GUID came from BookmarkSpecifics, or, in case it was missing, whether an originator_client_item_id of valid GUID format replaced it or it was left empty.

The tracker is fully operational (DeviceInfoTracker available, LocalDeviceInfo initialized, and Sync configured for writes). Prerequisite failed: DeviceInfoTracker is not available. Queries cannot be fulfilled. DeviceInfoTracker and LocalDeviceInfo available, but Sync is not configured for writes (e.g., signed out or Prefs sync disabled). Writes are blocked; data may be stale. DeviceInfoTracker available and Sync configured, but LocalDeviceInfo is missing (writes blocked). DeviceInfoTracker available, but both LocalDeviceInfo is missing and Sync is not configured. Sync is configured but initial preferences have not been downloaded. The user had their setting sync toggle off in their Google profile settings. As a result, cross-device setting import is unavailable. The user did not have any settings from remote devices to apply. This may happen if the user has not had any mobile devices before or if they never configured settingss on any of their previous devices. A snackbar was shown to the user allowing them to apply/undo their settings from a remote device.

Type of a network message sent from the client to the sync server.

The reason that triggered a configuration cycle, i.e. initializing DataTypeManager or changing the set of datatypes that should be actively syncing.

Type of change of a sync entity. Recorded once for every sync entity whenever it is commited to the server or updated from the server.

Possible errors that can trigger a sync error infobar.

Possible errors that can be returned by the sync server.

You might want to look at Sync.ThrottledSomeDataTypes to correlate this with throttling of a specific data type, or Sync.ThrottledAllDataTypes for throttling of the whole client. You might want to look at Sync.BackedOffDataType to see the per-type effect of this.

Equivalent to proto SyncEnums.GetUpdatesOrigin: represents a reason for a client to issue a GetUpdates request to the sync server.

Possible outcomes of handling incoming sync invalidations.

Specific error types encountered by the sync data types.

A step in the Extensions migration process, within the wider Sync-to-Signin migration.

A step in the ReadingList migration process, within the wider Sync-to-Signin migration.

A step in the Stats table cleanup process from the Account Password Store, within the wider Sync-to-Signin migration.

The outcome of the Themes deduplication process, within the wider Sync-to-Signin migration.

A step in the Themes migration process, within the wider Sync-to-Signin migration.