Device Portal data is out of sync
Symptom
-
A log message indicates "Retries exhausted", see screenshot:
-
A customer complains that …
-
a device he registered does not exist
-
a device he changed still displays "old" values
-
Actions
-
Perform a full synchronization of Device Master Data service or Device Monitoring service to OpenSearch, see: How to synchronize devices and machines to OpenSearch Ensure to synchronize the complete database to OpenSearch - speaking in terms of our current deployment scenario, this means that the request must be executed multiple times with an adjusted batchOffset.
Typical Cause
-
The synchronization of the state from Device Master Data service or Device Monitoring service to OpenSearch was not successful after a change of the data source. This could be the case if the concurrency was too high or if OpenSearch was temporary not available. Therefore, the synchronization of OpenSearch has to be triggered manually using the provided endpoints of the corresponding service.
Resolution
-
Synchronizing the complete data to OpenSearch should fix the problem.