Troubleshoot Calls in ADX

If you receive an error response to either a call to initiate the operation or a call to initiate output file delivery in ADX, use the sections below to troubleshoot errors.

Troubleshooting Guide

Use the tables in the sections below to understand and troubleshoot common errors you might receive in response to calls in ADX.

Region-Related Errors

Error Message	Step to Diagnose	Steps to Resolve
Asset not found (404)	Check that the asset and user are in the same region.	Verify the asset's region in ADX and update your user profile's region accordingly in the AWS Console.
Bucket region error	Verify the S3 bucket region.	Navigate to S3 Console, find the bucket, and confirm its region. Update settings if necessary.
The detected region of the input bucket is a non-US region.	None.	Contact LiveRamp Support.
The detected region of the input bucket is not a supported region and cross region support has not been enabled	Validate the bucket region.	Either enable cross-region support or move your data to a supported region.
The detected region of the input bucket is not a supported region for this Job ID.	Validate the bucket region.	Move your data to a supported region.

Input File Errors

Error Message	Step to Diagnose	Steps to Resolve
The input file header does not contain the target column specified in the request	Validate the input file.	Review the input file and modify it so that it contains the target column specified in the request.
One or more header column names in the input file contain spaces, tabs, or embedded newlines	Validate the input file.	Review the input file and modify it so that no header column names contain spaces, tabs, or embedded newlines.
The input file does not contain at least 100 unique rows	Validate the input file.	Review the input file and modify it so that it contains at least 100 unique rows.
The input file does not contain any data	Validate the input file.	Review the input file and modify it so that it contains data.
The output file contains fewer than 100 unique RampIDs	Validate the input file.	Add more rows of data to the input file.
Fewer than 95% of the rows in the input file pass LiveRamp privacy constraints	Validate the input file.	Remove unique columns that aren't being mapped in as identifiers and/or provide more input data.
The CID column names do not match across all sub-jobs. Expected: [cid column name] Found: [cid column name]	Validate the input file.	Review the API request body and modify it so that the CID column names match across all sub-jobs.

Payload-Related Errors

Error Message	Step to Diagnose	Steps to Resolve
Missing or invalid target_column	Validate the request body for required parameters.	Review the API request body and include the missing `target_column`. Double-check against API documentation.
Missing or invalid input_columns	Validate the request body for required parameters.	Review the API request body to include the missing `input_columns` and validate against API documentation.
The call to initiate identity resolution does not include a "target_columns" parameter or the parameter is empty	Validate the request body.	Review the API request body and modify it so that it includes a "target_columns" parameter and the parameter is not empty.
The call to initiate identity resolution does not include an 'execution_mode' parameter or an 'execution_type' parameter, or one or both of those parameters are empty	Validate the request body.	Review the API request body and modify it so that it includes an 'execution_mode' parameter or an 'execution_type' parameter, and that those parameters are not empty.
The call to initiate identity resolution does not include a 'client_id' parameter or a 'client_secret' parameter, or one or both of those parameters are empty	Validate the request body.	Review the API request body and modify it so that it includes a 'client_id' parameter or a 'client_secret' parameter, and that those parameters are not empty.
The 'target_columns' parameter does not contain either name or streetAddress (required when zipCode is provided)	Validate the request body.	Review the API request body and modify it so that the 'target_columns' parameter contains both a name and streetAddress.
The 'target_columns' parameter does not contain a zipCode column (required when streetAddress is provided)	Validate the request body.	Review the API request body and modify it so that the 'target_columns' parameter contains both a zipCode column.
The 'target_columns' parameter does not contain at least one of zipCode, phone, or email	Validate the request body.	Review the API request body and modify it so that the 'target_columns' parameter contains at least one of zipCode, phone, or email.
The 'target_columns' parameter contains an invalid name (such as a name containing special characters or longer than 254 characters)	Validate the request body.	Review the API request body and modify it so that the 'target_columns' parameter does not contain an invalid name.
The 'execution_type' contains an invalid execution type	Validate the request body.	Review the API request body and modify it so that it contains a valid execution type.
The 'config' parameter data type is not 'object'	Validate the request body.	Review the API request body and modify it so that the 'config' parameter data type is 'object'.
The 'config' parameter does not contain a 'deconflictionConfig' property	Validate the request body.	Review the API request body and modify it so that the 'config' parameter contains a 'deconflictionConfig' property.
The 'deconflictionConfig' parameter does not contain a valid value (such as 'standard' or 'maximized_1p_fidellity')	Validate the request body.	Review the API request body and modify it so that the 'deconflictionConfig' parameter contains a valid value.
The 'target_column' value is not a string	Validate the request body.	Review the API request body and modify it so that the 'target_column' value is a string.
The 'client_id' and 'client_secret' credentials are not valid	Validate the request body.	Review the API request body and modify it so that the 'client_id' and 'client_secret' credentials are valid.
The 'targetDomain' parameter is not a 4-character string	Validate the request body.	Review the API request body and modify it so that the 'targetDomain' parameter is a 4-character string.
The call to initiate identity resolution does not contain an 'authToken' parameter or is empty (authToken must be provided if runContext or targetDomain are included)	Validate the request body.	Review the API request body and modify it so that the call to initiate identity resolution contains an 'authToken' parameter and is not empty.
The call to initiate identity resolution does not contain a 'workflow_type' parameter or a 'workflow_sub_type' parameter, or one or both of those parameters are empty	Validate the request body.	Review the API request body and modify it so that it contains a 'workflow_type' parameter and a 'workflow_sub_type' parameter, and that both of those parameters are not empty.
The call to initiate identity resolution does not contain a 'client_id' parameter or a 'client_secret' parameter, or one or both of those values are empty	Validate the request body.	Review the API request body and modify it so that it contains a 'workflow_type' parameter and a 'workflow_sub_type' parameter, and that both of those parameters are not empty.
The call to initiate identity resolution does not contain a 'target_columns' parameter (required for cid_mapping execution flows)	Validate the request body.	Review the API request body and modify it so that it contains a 'target_columns' parameter.
The call to initiate identity resolution does not contain a 'targetDomain' parameter (required if the authToken is provided)	Validate the request body.	Review the API request body and modify it so that it contains a 'targetDomain' parameter.
The call to initiate identity resolution does not contain 'client_id' parameter or 'client_secret' parameter	Validate the request body.	Review the API request body and modify it so that it contains a 'client_id' parameter and a 'client_secret' parameter.
The call to initiate identity resolution uses a request method other than POST	Validate the request body.	Review the API request body and modify it so that it uses the POST request method.
The call to initiate identity resolution is missing the input request body or it is not valid	Validate the request body.	Review the API request body and modify it so that it contains a valid input request body.
The call to initiate identity resolution is missing the '[parameter name]' parameter or it is not valid	Validate the request body.	Review the API request body and modify it so that it contains a valid '[parameter name]' parameter.
The call to initiate identity resolution is missing a value for the 'deconflictionConfig' parameter (value required for CID mapping workflow)	Validate the request body.	Review the API request body and modify it so that it contains a value for the 'deconflictionConfig' parameter.
The 'inputs' parameter must not be empty	Validate the request body.	Review the API request body and modify it so that the 'inputs' parameter is not empty.
The call to initiate identity resolution cannot contain both an 'inputs' parameter and top-level 'input_s3', 'file_format', 'file_pattern', or 'target_columns' parameter	Validate the request body.	Review the API request body and modify it so that it does not contain both an 'inputs' parameter and top-level 'input_s3', 'file_format', 'file_pattern', or 'target_columns' parameter.
The call to initiate identity resolution is missing the '[parameter name]' parameter or it is not valid	Validate the request body.	Review the API request body and modify it so that it contains a valid '[parameter name]' parameter.
The 'file_format' parameter is missing or not valid	Validate the request body.	Review the API request body and modify it so that it contains a valid 'file_format' parameter.
The 'target_columns' parameter is missing a column name value	Validate the request body.	Review the API request body and include the missing target_columns. Double-check against API documentation.
The 'target_columns' parameter contains duplicate column name values	Validate the request body.	Review the API request body and modify it so it does not contain any duplicate column names.
The 'target_columns' parameter contains both a full parameter and a sub-element parameter	Validate the request body.	Review the API request body and modify it so that it does not contain both a full parameter and a sub-element parameter.
The 'target_columns' parameter contains more than the allowed number of elements	Validate the request body.	Review the API request body and modify it so that the 'target_columns' parameter does not contain more than the allowed number of elements.
The 'target_columns' parameter contains one or more unrecognized column types	Validate the request body.	Review the API request body and modify it so that the 'target_columns' parameter does not contain unrecognized column types.
The input file contains a column name wth the prefix "hashed_" that conflicts with a column name in the output	Validate the input file.	Review the input file and modify it so that any column names with the prefix "hashed_" do not conflict with a column name that you specified to be hashed in the output file.
The 'match_limit' parameter does not contain an integer between 1 and 10 (inclusive)	Validate the request body.	Review the API request body and modify it so that the 'match_limit' parameter contains an integer between 1 and 10 (inclusive).
The call to initiate identity resolution does not include a "target_column" parameter or the parameter is empty	Validate the request body.	Review the API request body and modify it so that it includes a "target_column" parameter and the parameter is not empty.

Permissions Errors

Error Message	Step to Diagnose	Steps to Resolve
AccessDeniedException	Check that the IAM user has necessary permissions.	Navigate to AWS IAM Console, locate the user, and attach the required permissions.
Could not connect to the endpoint URL	Check that the region is attached to the user or AWS profile.	Open AWS Console, go to 'My Account', and update the region to match with your ADX services.
500 Error (Lambda function failed to create a Job ID)	Ensure that the AWS region and user permissions are correct.	Double-check the region and permissions. If the issue persists, contact support with error details.
Your permissions were not found	None.	Contact LiveRamp Support.
You do not have permission for the requested workflow	None.	Contact LiveRamp Support.
The operation failed during authentication	None.	Contact LiveRamp Support.
The provided Auth token is not valid.	Validate the request body.	Review the API request body and modify it so that it contains a valid Auth token.
The input file header within the S3 bucket could not be read.	Validate S3 permissions.	Make sure that you've given LiveRamp the ability to read the S3 bucket or object, and that is not corrupted.
The operation failed during S3 bucket authentication.	None.	Contact LiveRamp Support.

Internal Errors

Error Message	Step to Diagnose	Steps to Resolve
The job failed to start	None.	Contact LiveRamp Support.
The operation failed during resolution and translation	None.	Contact LiveRamp Support.
The operation failed to append attribute columns	None.	Contact LiveRamp Support.
An internal error occurred.	None.	Contact LiveRamp Support.

Checklist to Verify Your Setup for LiveRamp Identity in ADX

To avoid errors, use the checklists in the sections below to verify that all the necessary native app setup steps have been successfully performed before executing an operation.

AWS Region Alignment

Region in Contract: Confirm that the AWS region you provided to LiveRamp during contract execution is consistent with your actual AWS services.
AWS CLI Region Check: Run aws configure get region to verify the AWS region for the IAM user or profile you're using.

Note

The ADX offer will be made and accepted in US-East-2 and API calls will be made from US-East-2.
The region you provide for your contract is where your buckets need to be. As long as your buckets are in US-East-1, your job (compute at LiveRamp's end for your job) will run in US-East-1 and will not incur cross-region data transfer costs. For bucket regions other than US-East-1 and US-West-2, you need cross region to be true in your incoming request and it will run in US-East-1.

IAM User and Permissioning

IAM User for ADX: Confirm that there is an IAM user configured specifically for ADX operations.
ADX Permissioning: Confirm that the IAM user has the required permissions for starting and polling jobs in ADX.
S3 Bucket Permissioning: Confirm that the IAM user has been granted read and write permissions for both the input and output S3 buckets.

S3 Bucket Setup

Input Bucket Configuration: Confirm that there is an S3 bucket exclusively dedicated for input files for LiveRamp processing.
Output Bucket Configuration: Confirm that there is a separate S3 bucket dedicated for output files from LiveRamp processing.
Bucket Policy Verification: Confirm that the bucket policies for the input and output buckets are aligned with LiveRamp's required permissions.
Bucket Accessibility Test: Execute aws s3 ls s3://<input-bucket-name> and aws s3 ls s3://<output-bucket-name> to verify IAM user access to the buckets.

In this section: