The Customers Debug Center provides a dedicated space to review customer records that failed during ingestion. It surfaces the error type, error message, and full customer payload so you can identify and resolve issues faster.
Open the Customers Debug Center
- Go to Customer Data in the left navigation panel.
- Click Profiles.
- On the Profiles page, click the Debug icon in the top-right corner.
- On the Debug Center page, go to the Customers tab.
The Customers Debug Center opens.
Filter errored customers
Use the filter bar at the top of the page to narrow down the customer records you want to review.
- Date range — Select the From and To dates for your search.
- Error type — Select an error category from the dropdown. By default, all error types are included.
- Customer identifier — Select the type of identifier to search by, such as Customer ID, Email, Phone Number, Cookie, or Device ID. By default, all identifiers are included.
- Limit — Enter the number of customer records to return in the results.
After setting your filters, click the Search icon to fetch matching customer records.
Availability and search behavior
Customer errors may take a few minutes to appear. Failed customer data can be searched in 7-day ranges, and each search returns up to 100 records.
Use recent searches
The Recent searches section shows the last 5 searches you ran.
Click a previous search to reload it. The filter bar is populated with the same criteria, and the results grid refreshes automatically.
Download search results
To download the results of your latest search, click the Download icon in the filter bar. The results are downloaded as a CSV file.
Review errored customers
Matching customer records appear in the Errored Customers grid. Select a record to inspect the payload and error details.
The grid shows the following details for each record:
- Timestamp — When the customer record was received.
- Customer identifier — The primary identifier for the customer, such as email, customer ID, or phone number.
- Error type — The category of the ingestion error.
- Error message — A short description of the failure.
Click a row to view the customer's JSON payload and review it to inspect customer fields, attribute values, and error context.
Fix erroneous records
Use the error type and customer payload to identify the root cause. Fix the customer data or source configuration, then resend the data. For errors that persist after retrying, contact support@blueshift.com.
Error types
The Customers Debug Center categorizes ingestion failures into specific error types. Use this table to understand what each error means and how to resolve it.
| Source | Error type | Description | Potential resolution |
|---|---|---|---|
| API | Unknown Error | Error root cause not known. Please reach out to support team. | An internal error occurred. Ingest the data again. If the error persists, contact support@blueshift.com. |
| API | User Profile Locked | This request could not be completed because the customer profile is currently being updated by another concurrent operation. | Retry the request after a short delay. If you are sending a high volume of requests for the same customer in parallel, consider sequencing them or adding a brief delay between updates to the same profile. Persistent failures on the same profile may indicate a stuck lock. |
| API | Invalid Customer Record | The customer profile data failed validation and could not be saved. | Review the field values in this request. Ensure at least one identifier is present and valid, all field values conform to the expected formats and length limits, and any subscription group IDs referenced are configured for your account. Correct the data and retry the request. |
| API | Record Locked | This customer profile could not be updated because it has been locked by an active data processing rule. | An internal error occurred. Ingest the data again. If the error persists, contact support@blueshift.com. |
| API | Too many users found on an identifier | The specified customer identifier is associated with too many customers. | The specified customer identifier is associated with too many customers. A customer identifier cannot be associated with more than 50 customers. |
| API | Forgotten User Access Error | The customer is marked as forgotten and cannot be updated. | The customer is marked as forgotten and cannot be updated. To re-enable, go to the customer profile and use the Unforget option. |
| API | Resource Not Found | The specified resource could not be found. | The data format does not match the expected column mapping. Please verify your file structure and field mappings, then re-upload. |
| API | Service Unavailable Error | The service is currently unavailable. Please try again later. | Review the flagged field values in this row. Ensure phone numbers follow the E.164 format, device tokens are valid, and no required fields are empty. Correct and re-upload. |
| Import | Row Parsing Error | This row could not be read because its format doesn't match the configured field mappings. | Verify that identifier fields (e.g., email, customer ID) are present, unique, and correctly formatted. If the error affects many rows, re-uploading may resolve transient issues. If the error persists, contact support@blueshift.com. |
| Import | Row Processing Failed | One or more fields contain invalid or unexpected values (e.g., invalid phone number, unsupported format). | Reduce the size of large text fields, arrays, or nested data in this row. If you must include large values, consider splitting them across multiple attributes or truncating where appropriate. |
| Import | Profile Save Failed | This row was processed successfully but could not be saved to the user profile store. This can happen due to conflicting or ambiguous identifiers, invalid profile data, or a temporary system issue. | Review the customer payload for conflicting or ambiguous identifiers and invalid profile data. Retry the upload. If the error persists, contact support@blueshift.com. |
| Import | Payload Too Large | This row exceeds the maximum allowed record size and was skipped. | Reduce the size of the customer record by trimming large text fields, arrays, or nested data. If you must include large values, consider splitting them across multiple attributes. |
Comments
0 comments