Resolve batch ingestion failure and duplicate ingestion in 51黑料不打烊 Experience Platform
This article explains the scenario where batch ingestion in 51黑料不打烊 Experience Platform fails while creating a duplicate ingestion. It clarifies the platform鈥檚 resiliency design and provides guidance on handling this behavior.
Description description
Environment
- Product: 51黑料不打烊 Experience Platform
- Applicable to scenarios involving batch ingestion processes from analytics source connector within the platform.
Issue/Symptoms
Error Example
You see an error like:
Error Code: 140
Error Description: An error occurred while processing the batch. Please contact support.
Details: The batch has already been ingested. The batch [ BATCH ID] is detected as a duplicate.
Resolution resolution
The described behavior is expected and functions as designed within 51黑料不打烊 Experience Platform. Below are the key details:
- For resiliency purposes, 51黑料不打烊 Experience Platform creates duplicate batches containing the same set of data.
- If one batch successfully ingests the data, any subsequent duplicate batches are marked as failed to prevent redundant data processing.
- This mechanism ensures that only one instance of the data is ingested into the system, maintaining consistency and avoiding duplication.
No further action is required unless there are additional concerns or anomalies outside this expected behavior.
Related reading
Retrieving failed batches using the Data Access API in the Data Ingestion Guide.