> For the complete documentation index, see [llms.txt](https://help.cymmetri.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.cymmetri.io/identity-hub/logs/reconciliation-history.md).

# Reconciliation History

The Cymmetri platform provides a centralized view for monitoring and auditing all reconciliation activities under the Audit Logs menu. This functionality offers administrators both a high-level summary and detailed drill-down views of each reconciliation job.

The Reconciliation History table, accessible via Audit Logs → Reconciliation History, has been enhanced to display the key reconciliation summary metrics directly in the table view.

This enhancement allows administrators to quickly assess the health and outcome of each reconciliation run without navigating to a separate detail page. The at-a-glance summary typically includes:

* **Pending Records**: Count of records awaiting processing.
* **Synced Records**: Count of records successfully synchronized (created, updated, or deleted).
* **Error Records**: Count of records that failed during the synchronization process.
* **Total Records**: The total number of records processed or considered in the run.

<figure><img src="/files/FyXLvi4pFjWi7ReT0gWk" alt=""><figcaption></figcaption></figure>

#### Detailed Reconciliation View (View History)

For a deeper analysis of a specific reconciliation run, administrators can select the View History option. This detailed view provides granular data organized across several key categories:

| **Modes**      | Sync field, Source attribute, Job completion time             | Specifies the primary attribute used for matching records, the source attribute used for data, and the final timestamp of the job's completion. |
| -------------- | ------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| **Conditions** | User does not exist in the Target System & exists in Cymmetri | Identifies users flagged for provisioning to the target system.                                                                                 |
| <p><br></p>    | User exists in Cymmetri & Target System                       | Identifies users flagged for profile update or validation across both systems.                                                                  |
| <p><br></p>    | User exists in Target System & does not exist in Cymmetri     | Identifies orphaned accounts in the target system, flagged for de-provisioning or review.                                                       |
| **Summary**    | Pending Records, Synced Records, Error Records, Total Records | The final statistical outcome of the reconciliation job.                                                                                        |

<figure><img src="/files/XXJfQWrvg1KBG4J5fR8a" alt=""><figcaption></figcaption></figure>

### Role Reconciliation Dashboard

The Role Reconciliation Dashboard is a specialized sub-page within the Recon History section dedicated to auditing and managing user role entitlements.

This dashboard provides administrators with the following granular details for each user involved in a role reconciliation activity:

| **Login**            | The unique login identifier of the user.                                                                                                                                    |
| -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Already Assigned** | The set of roles that the user held before the current reconciliation process was executed.                                                                                 |
| **Fetched**          | The roles for this user that were successfully retrieved from the target application during the reconciliation run.                                                         |
| **Newly Assigned**   | Roles that have been provisioned to the user as a direct result of the reconciliation logic.                                                                                |
| **To Be Removed**    | Roles identified by the reconciliation logic as needing to be revoked from the user's profile.                                                                              |
| **Status**           | The current state of a role assignment, indicating if the role has been removed, is currently under administrator review, or has been confirmed for continued assignment.   |
| **Actions**          | Interactive options allowing the administrator to drill down for further details on the specific role or to initiate a manual action (e.g., overriding the removal status). |

<figure><img src="/files/1rCJ7zHSKxgV9Q3FToOl" alt=""><figcaption></figcaption></figure>

To establish a new reconciliation job, please refer to the dedicated documentation on [Reconciliation Configuration.](/lifecycle-management/application-management/reconciliation-how-to.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.cymmetri.io/identity-hub/logs/reconciliation-history.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
