Troubleshoot

First, verify that both app references are bound:

CALL EDQ.CONFIG.register_reference(
  'experian_oauth_secret',
  'ADD',
  SYSTEM$REFERENCE('SECRET', 'EDQ_APP_CONFIG.AUTH.experian_oauth_secret', 'PERSISTENT', 'READ')
);

CALL EDQ.CONFIG.register_reference(
  'api',
  'ADD',
  SYSTEM$REFERENCE('EXTERNAL_ACCESS_INTEGRATION', 'experian_api_integration', 'PERSISTENT', 'USAGE')
);

If the references are correctly bound, verify the following:

• The external access integration is enabled.
• The network rule allows access to api.experianaperture.io, and the OAuth security integration uses the Experian token endpoint and valid client credentials.

The OAuth client is valid, but it does not include Address Validation entitlements. Contact your Experian account manager or Contact Support.

Make sure the relevant product has been configured and saved in the app. Address Validation needs a default country and dataset configuration, or a country override that maps to configured datasets.

For Address Validation, you can inspect the saved configuration:

CALL EDQ.CONFIG.get_address_config();

Grant SELECT on the source table or view to the installed application:

GRANT SELECT ON TABLE SOURCE_DB.SCHEMA.CONTACTS_TABLE TO APPLICATION EDQ;

Replace EDQ if the app was installed with a different application name.

Bulk source object names must use simple unquoted identifiers. If your table or column names need quotes, create a simple view with unquoted aliases and grant SELECT on that view to the app.

The where_clause parameter must be a filter expression only. Do not include the WHERE keyword, statement separators, comments, or data-changing statements.

Use:

'is_active = TRUE'

Do not use:

'WHERE is_active = TRUE; DROP TABLE ...'

Bulk result tables are created in EDQ.RESULTS. The app normalizes dots, spaces, and hyphens in the requested output table name to underscores.

For example, EMAIL RESULTS-2026 is created as EDQ.RESULTS.EMAIL_RESULTS_2026.

Use the Job dashboard or call:

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

Check the last_error, completed chunks and failed chunks. If jobs never start, confirm the app has the EXECUTE TASK and EXECUTE MANAGED TASK privileges requested during setup.

Open Job dashboard and use Chunk-level drilldown for the job ID. The last error usually identifies whether the failure is caused by source table access, invalid identifiers, unsupported filters, address country configuration, API connectivity, or a provider-side response.

Use RetryJob only after reviewing the error:

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

The app only retries failed chunks that were never started at Experian. This avoids additional provider cost for chunks that already started externally.

Address Validation needs a country that exists in the saved country_dataset_map. Configure the country and datasets on the Configure Address Validation page.

For bulk jobs, the optional country_column can override the default country per row. Values can be ISO3 codes or configured country names.

If source data contains country names rather than ISO3 codes, add mappings:

CALL EDQ.CONFIG.UpsertCountryIsoMapping('United States of America', 'USA');
CALL EDQ.CONFIG.UpsertCountryIsoMapping('United Kingdom', 'GBR');

Review the effective mapping:

SELECT country_name, country_iso, source
FROM EDQ.CONFIG.country_iso_mapping
ORDER BY country_name;

The optional datasets_column accepts a dataset string, a comma-separated list, or a JSON array. If datasets are supplied without a row country, the job uses the configured default country.

Single-record procedures return JSON as a string. Parse the response before using JSON path expressions:

SELECT
  result:result:confidence::STRING AS confidence
FROM (
  SELECT PARSE_JSON(EDQ.VALIDATION.Email('support@example.com')) AS result
);

Open Configure Phone Validation and disable premium options that are not required:

• Include number porting information
• Enable checking live status for US mobile numbers
• Enable checking live status for GB landline numbers