The Reconciliation Queue

The Reconciliation Queue is the workspace where incoming Configuration Items are matched against your CMDB, and where you resolve the records the engine cannot settle on its own.

If you have not turned reconciliation on yet, start with Getting Started with Reconciliation. This article is the reference for how the queue itself works.

How a record moves through the queue

Every record that arrives from an ingestion source runs through the same pipeline. The engine normalizes the incoming data, searches for matching Configuration Items, scores each candidate, and then either resolves the record automatically or parks it for a reviewer. Records that resolve on their own never need your attention. The queue is there for the rest.

Views and states

The queue segments records two ways at once.

Views split records by pipeline phase:

• All Reconciliations: every record.
• Identification: records still being matched to a Configuration Item.
• Review: records that have a resolved Configuration Item and proposed changes waiting.

State buttons then split each view by where the record sits:

• Open: still moving through the pipeline.
• Parked: paused, waiting on a reviewer.
• Completed: resolved and closed.

Filter to Parked to see only the records that need a decision from you.

The three parked statuses

A parked record is always at one of three statuses:

• Needs identification: the engine has not found a confident match. A reviewer identifies the right Configuration Item, or confirms the record is a new asset.
• Needs review: a Configuration Item is resolved and the proposed changes are waiting for approval.
• Ambiguous match: two or more candidates matched and the engine cannot tell which is correct. A reviewer picks the right one.

The reconciliation modal

Open any record to work it in the modal, which has two panels for the two halves of the job.

The Identify panel runs while a record is still being matched. It lists candidate Configuration Items with their confidence scores and what each one matched on, offers Create as new CI for genuinely new assets, and lets you search your account's own Configuration Items to link the record by hand when the engine did not find the match itself.

The Review panel runs once a Configuration Item is resolved. It shows a current-versus-proposed field comparison so you can see exactly what the update would change before committing it, with a note field to record your reasoning.

Finishing a record

From the Review panel, three actions close a record:

• Apply the proposed values to the matched Configuration Item: the incoming record becomes an update of that Configuration Item.
• Accept as a new Configuration Item: existing matched Configuration Items are left untouched.
• Dismiss: the record is rejected with no change.

If a reviewer resolved a record to the wrong Configuration Item, Back to identification undoes the identification and returns the record to matching.

In every case, the candidate matches are kept on the completed record, so there is always an audit trail of what the engine considered and what the reviewer decided.

Learned source links

When a source resolves to a Configuration Item, the system remembers that link so the same source pointing at the same device resolves straight to the same Configuration Item on later runs, without re-running the full match. A learned link is correctable: if it is ever wrong, fix it on the Configuration Item, and the system stops trusting a link once it no longer holds.