%kb_name - %short_descr - Knowledge Portal

Summary

This article provides scenarios of troubleshooting various errors and related issues encountered by customers when uploading batch files to Sitecore CDP.

AccessDenied error if request has expired

Uploading a batch file to CDP might fail with the following error:

FORCED ERROR: <?xml version="1.0" encoding="UTF-8"?>
<Error>
    <Code>AccessDenied</Code>
    <Message>Request has expired</Message>
    <X-Amz-Expires>3600</X-Amz-Expires>
    <Expires>2024-11-21T10:30:14Z</Expires>
    <ServerTime>2024-11-21T11:49:32Z</ServerTime>
    <RequestId>...</RequestId>
    <HostId>...</HostId>
</Error>

This error occurs if the batch file has not been uploaded within a one-hour period after the batch was submitted. Note that the response contains the expiration timestamp (Expires) as well as the current timestamp (ServerTime).

To resolve the issue, submit a new batch instead of the expired one.

"Not enough identifying information" error

Uploading a batch file to CDP might fail with the following error:

{"ref":"UUID","code":"400","message":"Not enough identifying information"}

The error occurs if the value of the provider attribute in the identifiers array of JSON objects in the batch file does not correspond with the value of the Identity Rule in the CDP environment.

To resolve this issue, do the following:

In the CDP UI, check the value of the Identity Rule – the identifier.provider value.
In the batch file, check the value of the provider attribute in the identifiers array.
Adjust those values to be the same and then upload the batch file again.

The error "Not enough identifying information" might also occur in the following scenarios:

When migrating xDB contacts to CDP – if the identity rules in the Sitecore Connect Recipe do not match the identity rules in CDP.
When trying to update the existing in CDP guest profiles of the guestType "visitor". Note that the Batch API Guest data model requires that guests have the guestType ''customer" to be uploaded to CDP.

"Entity: Order, Attribute: price is invalid: must be greater than or equal to 0" error

The following error might occur when uploading a batch file to CDP:

{"ref":"UUID","code":"400","message":"Entity: Order, Attribute: price is invalid: must be greater than or equal to 0"}

This error occurs when the price of the order is negative and the batch is uploaded in insert mode.

To resolve the issue, use "mode":"upsert" in the batch file.

Errors in the format of attributes

When uploading a batch file to CDP, customers might encounter a couple of errors that signify that the attributes of the entities (guests and orders) have the wrong format:

```
{"ref":"UUID","code":"400","message":"Failed to parse import line"}
```
This error occurs if any attribute of the guest or order has been put in the wrong format.

{"ref":"UUID","code":"400","message":"Entity: Order, Attribute: contact.email is invalid: not a well-formed email address"}

This error occurs if the email address of the guest has failed the email validation.

To resolve the issue, check all the entities (guests and orders) in the batch file and make sure that the records meet the formatting requirements of the documentation:

Duplication of guests or orders

Customers might face an issue when duplicate guests or orders have been created in CDP.

Note: It is required that a batch file contain no more than one record associated with the same guest or order. This way no duplicates will be added.