The Run step is where the match actually executes. A progress bar driven by server-sent events (SSE) shows live status as the engine moves through each pass. You can watch, walk away and come back, or navigate elsewhere in the app — the job runs to completion regardless.
What you see
Progress bar
A segmented bar showing progress through each phase of the match:
- Prep — loading cleansed data into the engine's memory
- Block building — creating candidate groups via ZIP or phonetic codes
- Scoring — comparing candidate pairs and computing scores
- Classification — assigning match/review/unmatched to each source row
- Summary generation — the Genie writes the narrative and builds the result set
Each phase shows a percentage; current phase's bar fills as it progresses. The full bar fills as the job completes.
Live stats
Below the progress bar, live counters update as the engine works:
- Rows processed
- Candidates evaluated
- Matches found (so far)
- Elapsed time
Status messages
The Genie surfaces key events as they happen:
- "Blocking produced 42 groups averaging 180 candidates each."
- "All source rows have been scored. Classifying..."
- "Review queue: 847 pairs flagged."
These are also captured in the job's event log and available on the job detail page.
How long it takes
Match time scales with source rows × master rows (roughly), reduced by blocking. Approximate runtime on a standard job:
| Source rows | Master rows | Typical runtime |
|---|---|---|
| 100 | 10,000 | < 1 second |
| 1,000 | 50,000 | 2–5 seconds |
| 10,000 | 100,000 | 15–30 seconds |
| 100,000 | 250,000 | 1–3 minutes |
| 500,000 | 1,000,000 | 5–10 minutes |
Bigger files take longer; enabling phonetic matching or ZIP radius roughly doubles runtime (bigger candidate pools).
Walking away
The match continues running server-side even if you close the tab. When you come back:
- The dashboard shows the job's current status
- The jobs list shows it with a
processingbadge - Clicking into it shows the same live progress
Completed jobs are available until you delete them (or until master/source files retention expires).
If it fails
Fatal errors during matching surface on the Run screen with a clear message and (usually) a suggested fix. Common failures:
- Out of memory — your file is too large for your tier. Upgrade or split the file.
- Malformed source data — a specific row or column is unparseable. Jump back to Cleanse to inspect.
- Upstream service issue — rare, transient. Retry the match after a moment.
Failed jobs don't count against your match-jobs quota.
Advancing
When the match completes, the wizard auto-advances to Review. You can also click View results at any point — all partial results are accessible even mid-run (for long-running jobs).
Related reading
- Jobs — the full job detail page
- How matching works — what happens under the hood
- Troubleshooting — failure recovery