The Events Debug Center provides a dedicated space to review events that failed during ingestion. It surfaces the error type, error message, and full event payload so you can identify and resolve issues faster.

Open the Events Debug Center

Go to Customer Data in the left navigation panel.
Click Events.
On the Events page, click the Debug icon in the top-right corner.

The Events Debug Center opens.

Filter errored events

Use the filter bar at the top of the page to narrow down the events you want to review.

Date range — Select the From and To dates for your search.
Event name — Select a specific event from the dropdown. By default, all events are included.
Error type — Select an error category from the dropdown. By default, all error types are included.
Limit — Enter the number of events to return in the results.

After setting your filters, click the Search icon to fetch matching events.

Availability and search behavior

Errored events are available for the past 12 months. The informational message below the filter bar describes the supported search window and result limits.

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 events

Matching events appear in the Errored Events grid. Select an event to inspect the payload and error details.

The grid shows the following details for each event:

Timestamp — When the event was received.
Event name — The name of the event.
Error type — The category of the ingestion error.
Error message — A short description of the failure.

Click a row to view the event's JSON payload, and review the payload to inspect event fields, attribute values, and error context.

Fix errored events

Use the error type and event payload to identify the root cause. Fix the event data or source configuration, then resend the event. For errors that persist after retrying, contact [email protected].

Error types

The Events Debug Center categorizes ingestion failures into specific error types. Use this table to understand what each error means and how to resolve it.

Error type	Description	Potential resolution
Event Name Missing	The event payload does not include an event name.	Ensure the payload includes the event name field.
Indexing Error	An internal error occurred while indexing the event.	Ingest the data again. If the error persists, contact [email protected].
Attribute Limit Exceeded	The number of indexed attributes has reached the account limit.	Ingest the data again. If the error persists, contact [email protected].
Missing Identifier	The event payload is missing a customer identifier (cookie, device_ids, email, email_hash, or retailer_customer_id).	Include at least one identifier such as uuid, customer_id, email, device_id, or cookie.
Missing Product Ids	Product identifiers are missing from the event payload.	Ensure the event payload includes valid product identifiers.
Invalid Device Id	The device_id in the event payload is not valid.	The Device ID must be between 10 and 100 characters long.
Invalid Email	The email address in the event payload is not valid.	Provide the email in the correct format. Maximum 256 characters allowed.
Invalid Product	The product referenced in the event payload was not found in the catalog.	Ensure the product in the payload exists in the catalog.
Parsing Error	The event payload could not be parsed.	Check that the payload is valid JSON and correctly structured before resending.
Unknown Error	An unexpected internal error occurred during ingestion.	Upload the data again. If the error persists, contact [email protected].
User Not Found	The customer associated with the identifier in the payload was not found.	Verify that the customer identifier exists in your Blueshift account.
User Lock not acquired	The system could not lock the user record for processing.	Ingest the data again. If the error persists, contact [email protected].
Too many users found on an identifier	The identifier matches more than the allowed number of customers.	A customer identifier cannot be associated with more than 50 customers.
Invalid User Attributes	One or more user attributes in the payload have invalid values.	Check that attribute values meet format requirements: gender must be 'male', 'female', or 'unknown'; unsubscribed must be 0 or 1; joined_at must be ISO8601 format; firstname/lastname max 64 chars.
Invalid Customer Id	The customer_id in the event payload is not valid.	The customer ID can have a maximum of 128 characters.
Transaction Indexing Error	An internal error occurred while indexing transaction data.	Upload the data again. If the error persists, contact [email protected].
Event Verification Error	The event failed one or more verification checks during ingestion.	Review the event payload for missing or invalid required fields.
Invalid Event Attributes	One or more event attributes in the payload are invalid.	Ensure event attribute names and values match the expected schema.
Transaction Processing Error	An error occurred while processing the transaction data.	Upload the data again. If the error persists, contact [email protected].
UTX Fetch Account Config Error	An error occurred while fetching the account configuration.	Contact [email protected].
Forgotten User Access Error	The customer is marked as forgotten and cannot be updated.	Go to the customer profile and use the Unforget option to re-enable updates.