Operational history

Review reconciliation runs and import jobs for any Matcher context on one operational history page, with live-refreshing tables and status badges.

The Operational History page in the Matcher UI provides a centralized view of reconciliation runs and data-import jobs for a context. The page stacks two tables: Run history and Import jobs.

Export jobs are not part of this page — they live on the Reporting → Exports page, next to the rest of reporting. See the Exports surface for report downloads.

Accessing the Operational History page

---

Navigate to Matcher → Reporting → Operational History in the left sidebar.

Filtering by context

---

A context selector in the page header scopes the page. Select a context to view its runs and import jobs; the status rail below the header confirms the context you are looking at.

Run history

---

The Run history table lists reconciliation runs for the selected context, newest first. While any run is still in progress, the table refreshes automatically every few seconds and shows a Live indicator.

Column	Description
Run	Short run identifier, linking to the run’s detail page
Mode	Either DRY_RUN (preview only) or COMMIT (results persisted)
Status	Current run status displayed as a colored badge
Matches	Number of match groups created
Unmatched	Total unmatched transactions from both sides, highlighted when greater than zero
Split	A mini balance bar visualizing the matched share of the pool
Started	When the run started processing
Exceptions	A View exceptions link that opens the exceptions queue filtered to this run

You can filter the table by run Status and by a From/To date window. Pressing Enter on a focused row opens the run’s detail page — the same destination as the Run link.

Run statuses

Status	Description
QUEUED	The run is queued and waiting to be processed
PROCESSING	The matching engine is actively processing transactions
FINALIZING	The engine is finishing the run and writing results
COMPLETED	The run finished successfully
FAILED	The run encountered an error

Run modes

Mode	Description
DRY_RUN	Simulates the reconciliation without persisting results — useful for testing rules
COMMIT	Executes the reconciliation and persists all match results

Import jobs

---

The Import jobs table lists the data-ingestion jobs for the selected context. Like the run history, it shows a Live indicator and refreshes while jobs are in flight.

Column	Description
File	Name of the uploaded file
Status	Current job status as a colored badge; a job that finished with row failures is flagged Completed with errors
Rows	Rows persisted out of the total parsed, with a note when duplicates were dropped
Failed	Number of rows that failed ingestion
Created	When the ingestion job was created
Completed	When the ingestion job finished

Jobs with failed rows include a View errors link to the per-row error report.

Ingestion job statuses

Status	Description
QUEUED	The job has been submitted and is waiting to be processed
PROCESSING	The file is currently being ingested
COMPLETED	The file was successfully ingested
FAILED	The ingestion failed — check the file format and try again