Accessing the Run match panel
Navigate to Operate → Reconciliations in the left sidebar. The Reconciliations screen shows the run history for the selected context, with the Run match panel for starting a new run. If you have not selected a context, the Console selects the first available one automatically; use the context selector to choose another. If no contexts are available, the screen shows an empty state instead of the panel.
Run modes
Choose a run mode from the Mode dropdown before starting:
Starting a run
Click Run match. The Console sends
mode without async, so the run executes synchronously; it is not queued. Its response carries a terminal run status. Status badges can show the following states:
The Console fetches the run status after every launch. Its synchronous launch reaches a terminal status on that first fetch, so it does not continue refreshing. An API run submitted with
async: true responds QUEUED and needs continued polling until COMPLETED or FAILED; asynchronous submission requires the match-run worker to be enabled, otherwise the service rejects the request instead of queueing it. On the run-detail page for a non-terminal run—for example, an asynchronous run opened from run history—the Console refreshes every two seconds for up to 90 attempts (about three minutes). Stop watching stops only the local refresh, not the server-side run; Recheck status restarts the refresh.
The Console blocks the launch only when its pre-run check successfully returns a total of zero transactions. It then shows a warning and an Import data button. While that check is loading or fails, the Console does not claim that the context is empty and leaves the launch available. If a run still completes with zero candidates on both sides, the Console shows an import warning instead of the statistics or View match groups.
Reviewing results
For a completed, non-empty run with statistics, the panel shows a headline Matches figure and a breakdown of per-side statistics:
Above the breakdown, the Console can show summary visualization for the statistics returned by the run.
Dry-run results
A dry run creates and completes a persisted run record with aggregate statistics, including calculated candidate, match, and unmatched counts. Its two exception statistics are explicitly zero. It does not persist match groups or items, transaction-result changes, or exceptions, so the Console presents the run as a statistical preview rather than persisted group-by-group results. Although View match groups can still open the run detail, no match groups were written by a dry run. Use the statistics to adjust rules, then switch to Commit and run again to persist results.
Viewing detailed results
After a completed Commit run, click View match groups to open the run detail and inspect the persisted groups for that run. A dry run has no persisted groups to inspect; use its summary statistics instead.