AEP Batch Ingestion Error | Updates are not supported for events

[sampathb23]

Hi, Many batches are failed during Ingestion with the error "Updates are not supported for events.Updates not supported for events". Issue arises in production sandbox after few days the WebSDK Source went live. For the initial few days, we haven't received those errors in AEP.  At the moment, more than half of the batches are being failed with this error. We have only configured the Experience Event schema as we are fetching behavioural data from website via WebSDK. When we reported this issue to Adobe Support, we have been informed by Adobe Technical support engineer that we should also have an Individual Profile schema configured for this error not to occur. I don't find proper information in the adobe helpex documentation or forums. Can anyone please help if you have any idea or face similar error?

Thanks & Regards,

Sam

[ranjithd · Accepted solution]

The error notice "Updates are not supported for events." generally indicates you're attempting to edit or alter events that have already been ingested into Adobe Experience Platform (AEP). Once an event has been ingested, it cannot be changed or updated; instead, send a new event to AEP with the updated information.

There are several possible causes for this issue during ingestion:

i) Change in data structure: The data structure of the events delivered to AEP may have changed after the WebSDK Source went live. If this is the case, the new data may be viewed as an update to existing events rather than as new events.

ii) Problems with the data ingestion pipeline: A problem with the data ingestion pipeline may be causing events to be treated as updates rather than new events. This might be due to an AEP misconfiguration, a problem with the data processing pipeline, or other issues.

iii) Changes to the AEP configuration: If you've made any changes to the AEP configuration since the WebSDK Source became live, these changes may have an impact on how events are ingested and processed.

To remedy this issue, you must ensure that the events submitted to AEP are new and not changes to old events. Here are a few recommendations:

1. Examine the data structure: Examine the data structure of the events submitted to AEP to confirm that it conforms to the anticipated format. If the data structure has changed, you may need to adjust your implementation to transmit new events rather than updates.

2. Examine the AEP configuration: Examine the AEP settings to confirm that no problems with the data ingestion pipeline are causing events to be interpreted as updates. This may entail examining the setup of data processing pipelines, data schemas, and other AEP environment components.

3. Examine the code for any changes: Examine any modifications to the implementation code that have occurred since the WebSDK Source became live to confirm that they are not causing events to be treated as updates.

If you are unclear how to remedy this issue, you should contact Adobe support for more assistance.