The feature usage state for checkout/checkin is stored locally on the device, and also updated in the cloud during checkout and checkin operations. However, this synchronization is not continuous or automatic beyond those operations.
If the same entitlement is used across multiple devices or activations (e.g. in a shared or multi-seat setup), it’s important to manually synchronize the local and cloud states to maintain consistency. You can do this using the Activation.PullRemoteState() method.
Whether you need to manually sync depends on your entitlement configuration:
Single-seat entitlement (one activation at a time):
Typically no additional sync is necessary, as only one device can check out features at any given time.
Multi-seat entitlement (multiple activations sharing seats):
Manual syncing is recommended to ensure that all devices reflect the correct feature availability and usage.