Here are some tips to help you troubleshoot event imports in Blueshift.
Download error logs
When you view the events stream, you can also look at errors and download the error log. Go to the error events tab and click Export error data to download the error log.
Import Errors
Here are some of the errors you might encounter when you import events into Blueshift. For more information required fields and data formats, see Import events data.
| Error Message | Description |
| Missing required fields | Event data must include at least one customer identifier - uuid, customer_id, email, device_id, or cookie. |
| User identifier missing. No valid identifier found | A valid customer identifier was not found. Event data must include at least one customer identifier - uuid, customer_id, email, device_id, or cookie. |
| Email is not in proper format | The email is not in the correct format. |
| email is too long (maximum is 128 characters) | The email can have a maximum of 128 characters. |
| Retailer customer is too long (maximum is 128 characters) | The customer identifier can have a maximum of 128 characters. |
| products not in catalog | The product from the event data is not found in the catalog. |
| UserLockError: Multiple updates on the same user | A lock is not acquired on the customer being updated. This error occurs if there are multiple events for the same customer within a short period of time and if the customer data is being updated for another event. |
| please provide a timestamp |
A timestamp is required for an event. The timestamp might be missing or might be in the incorrect format. The timestamp should be in ISO8601 format. For example, "2017-08-08", "2017-08-08T17:42:32Z". |
| Internal Connection Error: uts_error= | An internal error occurred. Upload the event data again. If the error persists, contact support@blueshift.com. |
| Internal Conflict Error: uts_error= | An internal error occurred. Upload the event data again. If the error persists, contact support@blueshift.com. |
| Internal Server Error: uts_error= | An internal error occurred. Contact support@blueshift.com. |
| User was marked as forgotten: uts_error= |
The customer is forgotten. Forgotten customers cannot be updated. To start tracking the customer again, you can go to the customer profile and Unforget the customer. |
| BadRequest Error: error= | An internal error occurred. Contact support@blueshift.com. |
| Firefly error status=500 \{\\\"errors\\\":\\\"timeout: get product_by_sku query timeout\\\"}\ | An unknown error occurred. Contact support@blueshift.com. |
Other issues
Q. Why is the recurring events import task not importing any events?
Ensure that the file that is being imported from S3 or Snowflake has data.
Q. Why are events failing with "Product not found in Catalog" error even though the product is present in the catalog?
Ensure that the Product ID that you are passing in the event uses the correct case. The Product ID is case sensitive.
Comments
0 comments