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.
Open Job dashboard and complete Submit a new validation job.
| Field | Description |
|---|---|
| Validation type | Address, Email, or Phone. |
| Source table (fully qualified) | Fully qualified table or view name, for example SOURCE_DB.SCHEMA.CONTACTS_TABLE. |
| Address column, Email column, or Phone column | Column to validate. The field label changes based on the selected validation type. |
| Unique ID column | Stable ID column used as record_id in results. |
| Output table name | Result table name to create in the app's RESULTS schema. |
| Filter (optional) | Optional filter expression without the WHERE keyword. |
| Country column (optional) | Address jobs only. Optional per-row country override. |
| Datasets column (optional) | Address jobs only. Optional per-row dataset override. |
Select Submit job to queue the job. The app validates the inputs before submitting. It rejects SQL statement separators and comment tokens such as ;, -- and /* */.
Use Active and recent validation jobs to review the 50 most recent jobs, including job ID, validation type, status, output table, total records, processed records, percentage complete, chunk counts, timestamps, and last error.
Select Refresh jobs to reload the table.
| 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 already been submitted may still complete and write results. |
Check one job:
CALL EXPERIAN_DATA_VALIDATION.JOBS.Status('<job_id>');
List the 50 most recent jobs:
SELECT * FROM TABLE(EXPERIAN_DATA_VALIDATION.JOBS.List());
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.
Use Manage jobs to cancel or retry jobs.
Use Cancel a job to submit a cancellation request:
CALL EXPERIAN_DATA_VALIDATION.JOBS.Cancel('<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.
Use Retry failed job to requeue failed chunks:
CALL EXPERIAN_DATA_VALIDATION.JOBS.Retry('<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.
Use Chunk-level drilldown in Job dashboard to inspect:
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.