Every time you click Start process (or Run Data Pipeline), DQE One Standalone creates a new run and processes it in the background: you can navigate away and come back later, the Results screen reflects current progress automatically. Only one of your runs executes at a time — if you start several, the rest wait in a queue.
Where to monitor a run
- Processes list — each row shows the related process's last run as a Status badge ("No Run" if it has never run). Click the row to open the process and see the full Results screen.
- The process's own Results tab (step 4 of the process wizard) — this is the main monitoring and action screen, covered below.
- Overview page — lists your 5 most recently run processes with Name, Created date and Status.
Scheduler → History tab — a list of every past run across all your processes, with Name, Run date, Volume (records processed) and Status.
This list is useful to see that a process ran and how it went, but clicking a row always opens the process's current Results screen — not a frozen view of that specific past run. You can't drill into the detail of an older run once a more recent one exists.
Run statuses
A run moves through a fixed sequence of statuses. The sequence depends on the data source:
| Source | Sequence |
|---|---|
| CSV file or SFTP | Started → Reading → In Progress → Writing → Finished |
| Salesforce, Dynamics, Postgres, BigQuery or Snowflake | Started → Creating DQE Fields → Reading → In Progress → Writing → Finished |
| Status | Meaning |
|---|---|
| Started | The run has been queued or has just begun. |
| Creating DQE Fields | Technical fields are being prepared on the source object before extraction (connector sources only). |
| Reading | Source data is being extracted/imported. |
| In Progress | The core processing (check, format, dedup…) is running. |
| Writing | Results and the output file are being written. |
| Finished | Completed successfully — results are ready to use. |
| Failed | Stopped because of an error, or because you clicked Stop process (see below). |
For a Unify Process run, while status is In Progress an extra live widget shows the matching engine's own phases: "Phase one: Creating Keys", "Phase two: processing {current}/{total}", then "Finalizing...", with a percent bar.
There is no "Killed" status. If you stop a run yourself, it ends up as Failed, with an error message naming you and the time you stopped it.
The Results screen
At the top: Process name, Process type, Record type and Last Run (timestamp of the current run). Below that, a step-by-step progress bar tracks the sequence above; if a step fails, hovering its icon shows the underlying error message. Once the run reaches a final state, the item count appears as "{count} items".
Buttons shown depend on the process kind and its current run status:
| Button | What it does | Shown for |
|---|---|---|
| Start process | Launches a new run. | No run yet, or the last run is Finished/Failed. |
| Stop process | Cancels the running job (see below). | See "Stopping a run" below — not every kind, and not at every stage. |
| Sync | Writes results back to the source object. | Connector sources (Salesforce, Dynamics, Postgres, BigQuery, Snowflake), or any process with a configured output. |
| Merge / Unmerge | Applies or reverts the RuleSet's merging rules. | Check Postal Address, Check B2B and Unify Process, on connector sources only. |
| Report | Downloads a PDF quality-code report. | Process kinds that produce quality codes. |
| Export | Downloads the result file. | All kinds (Audit has its own dedicated Export, see below). |
| Display | Opens "Configure table display" to choose and reorder visible result columns. | All kinds. |
Each action asks for confirmation first — for example, Start process shows "You are about to start the process. Do you want to continue?", and Sync/Merge/Unmerge have their own equivalent prompts.
Downloading results and logs
- Export downloads a CSV file named
{process name}_{run}_{date}.csv. For a Unify Process on a CSV or SFTP source, this instead downloads a ZIP with two files:..._DQE_DUPS.csv(the duplicates found) and..._DQE_DEDUP.csv(the deduplicated output). - Export Run Logs downloads the run's technical log as a
.logfile. It's only available once the run has reached Finished or Failed. - Report downloads a PDF quality-code report; for an Audit process, use its own Export button instead, which downloads a PDF of the audit results.
Stopping a run
Click Stop process, then confirm ("You are about to stop the process. Do you want to continue?"). Whether this button is available depends on the process kind and how far the run has gone:
- For Find & Replace, Format, Unify Process and Audit, Stop process is available for the whole duration of the run.
- For Check Email, Check Phone, Check Postal Address, Check B2B and Index Records, Stop process is only available early on — while the run is still Started or Reading. Once it reaches In Progress or Writing, it has to finish (or fail) on its own.
A stopped run ends with status Failed and no usable output file — there's nothing to export from it.
Running again
There's no action to replay a specific past run. Start process always launches a brand-new run from the process's current saved configuration, replacing the previous run's results. If you need different results from the same data, change the process's configuration before starting it again rather than looking for a per-run "edit and relaunch" option.
Getting notified about a run
Open My Account → Notifications and enable email and/or push notifications per process kind ("Process Check Duplicate", "Process Check Email", etc.). When enabled, you'll receive:
- On success: "✅ Success: Process {name} completed successfully".
- On failure: "⚠ Warning: Process {name} encountered an error", with the error details included.
DataPipeline runs work differently: you'll always get an email when a pipeline finishes or fails, regardless of your Notifications settings above — there's no per-kind checkbox to turn it off.
Monitoring a DataPipeline run
A DataPipeline chains several processes together — see Configure a DataPipeline in DQE One Standalone for how to build one. Monitoring it uses the same statuses as above, but its own screen and button set:
- Run Data Pipeline starts it.
- Stop Pipeline stops whichever step is currently running and ends the whole pipeline as Failed — confirmation text: "You are about to stop the running data pipeline. All pending steps will be cancelled. Do you want to continue?". The same stage-dependent restriction as above applies to Check Email/Phone/ Address/B2B steps.
- View Results opens a results sidebar once the pipeline has finished.
The pipeline's progress indicator shows each step individually, so you can see which step is running and which ones have already finished or failed.
Related to