Monitor jobs

Bulk validation jobs are processed asynchronously by the app's managed orchestration task. Use the Job dashboard page or SQL procedures to submit jobs, track progress, and manage failures.

Submit a job from the dashboard

Open Job dashboard and complete:

Field Description
Validation type Address, Email, or Phone.
Source table Fully qualified table or view name, for example SOURCE_DB.SCHEMA.CONTACTS_TABLE.
Validation column Address, email, or phone column to validate.
Unique ID column Stable ID column used as record_id in results.
Output table name Result table name to create in EDQ.RESULTS.
Filter Optional filter expression without the WHERE keyword.
Country column Address jobs only. Optional per-row country override.
Datasets column Address jobs only. Optional per-row dataset override.

The app validates the inputs before submitting the job. It rejects SQL statement separators and comment tokens such as ;, -- and /* */.

Job statuses

Status Meaning
queued The job has been created and is waiting for the orchestrator to snapshot source rows.
running One or more job chunks are currently being processed..
completed All chunks completed successfully.
partial Some chunks completed successfully, while others failed. Query the output table for completed rows.
failed All chunks failed, or the job could not be started.
cancelled Cancellation was requested. Chunks not yet started are cancelled. Provider batches that have been already submitted may still complete and write results.

Monitor with SQL

Check one job:

CALL EDQ.VALIDATION.JobStatus('<job_id>');

List the 50 most recent jobs:

SELECT * FROM TABLE(EDQ.VALIDATION.JobList());

The job status response includes the source table, output table, total records, total chunks, completed chunks, failed chunks, processed records, percent complete, and last error.

Cancel a job

CALL EDQ.VALIDATION.CancelJob('<job_id>');

Cancellation stops local work that has not started at Experian. Chunks that are already being processed, continue to completion so their results can still be written.

Retry a job

CALL EDQ.VALIDATION.RetryJob('<job_id>');

Retry applies to jobs in failed or partial status. The app only requeues failed chunks that were not submitted to Experian. Chunks that already started externally are skipped to avoid creating additional provider charges.

Chunk drilldown

Use Chunk-level drilldown in the Job dashboard to inspect:

  • Chunk ID
  • Chunk status
  • Offset and size
  • Records processed
  • Retry count
  • Submitted and completed times
  • Next poll time
  • Last error

This is the fastest place to identify whether a partial job failed because of source table access, API connectivity, configuration, or a provider-side error.