Skip to main content
Version: Omada Identity Cloud

Handling history tracking inconsistencies

During data transfer, the following actions are performed:

  • Inconsistent entries are marked as failed.
  • Failed entries are marked for a retry action.
  • Error cleanup is performed.
  • The watermark is reset.
  • Extension attributes are maintained.

Due to the asynchronous nature of transferring data to ODS, the order of transferred data might not be appropriate (for example, the resource is loaded before the resource folder). This results in marking objects, lacking their dependencies, as inconsistent. Afterwards, the inconsistencies are reevaluated, and if the counter reaches 5 failed attempts, the status is changed to permanently inconsistent.

note

The 5 attempts at reevaluating inconsistencies amount to around 25 minutes.

Number of inconsistencies​

The number of inconsistencies displayed in the Analytics widget may differ from the number shown in the detailed view. The widget shows an aggregated count: if a single user or object has multiple inconsistencies, it is counted once. The detailed view lists each inconsistency separately, resulting in a higher total.

info

The detailed view has a limitation of 1000 rows, so environments with a high number of inconsistencies may see a truncated list.

Inconsistencies troubleshooting​

The inconsistencies are exceptions that result from an improper configuration or malfunctions. Below, you can find scenarios that may lead to the permanently inconsistent status and suggestions on how to resolve them.

  1. Transient error in infrastructure:

    Probable cause: The data has been transferred, but with a substantial delay.

    Proposed solution: Reset the inconsistency flag, resulting in a reattempt of the history tracking feature.

  2. Data error:

    Probable cause: The data object has an incorrect value in a reference property.

    Proposed solution: Update the object in the Enterprise Server. The object is then synchronized, resolving the inconsistency.

  3. Incorrect mapping:

    Probable cause: The advanced configuration of mapping from ODS to ODW is incorrect.

    Proposed solution: Correct the mappings and reset the inconsistency flag.