Failed records(batch ingestion) due to MaxIdentities and InvalidXdm error | Community
Skip to main content
SahuSa1
SahuSa1
Level 3
July 7, 2025
Solved

Failed records(batch ingestion) due to MaxIdentities and InvalidXdm error

  • July 7, 2025
  • 1 reply
  • 671 views

Hi,

 

There are few records which have failed to ingest (to a dataset having batch ingestion) due to MaxIdentities error and InvalidXdm error. For MaxIdentities it says "Identities size is more than defined limit 20 for Ingestion" and for InvalidXdm it says "Invalid ECID found. Skipping this record".

 

Could someone please help me understand what does the MaxIdentities error mean? And if there is any way to stop these records from failing?

  

Thanks,

Sambit

Best answer by KumarRishii
Both MaxIdentities and InvalidXdm errors are common in batch ingestion pipelines in AEP.

To fix MaxIdentities Error:

Limit identity types to 20 or fewer per record.
Remove unused or duplicate identity namespaces.
Add pre-ingestion validation to filter or truncate excess identities.

To fix InvalidXdm (Invalid ECID) Error:

Ensure ECID is a valid, non-empty string (usually 38 characters).
Confirm the identity namespace is exactly "ECID" (case-sensitive).
Validate and clean ECIDs before ingestion.

I will suggest you to  add pre-validation logic to your ETL or Data Prep pipeline to catch and correct these issues before ingestion.

1 reply

KumarRishii
KumarRishiiAccepted solution
Level 5
July 7, 2025
Both MaxIdentities and InvalidXdm errors are common in batch ingestion pipelines in AEP.

To fix MaxIdentities Error:

Limit identity types to 20 or fewer per record.
Remove unused or duplicate identity namespaces.
Add pre-ingestion validation to filter or truncate excess identities.

To fix InvalidXdm (Invalid ECID) Error:

Ensure ECID is a valid, non-empty string (usually 38 characters).
Confirm the identity namespace is exactly "ECID" (case-sensitive).
Validate and clean ECIDs before ingestion.

I will suggest you to  add pre-validation logic to your ETL or Data Prep pipeline to catch and correct these issues before ingestion.
    SahuSa1
    SahuSa1Author
    Level 3
    July 7, 2025

    Hi @kumarrishii , Thanks for your quick reply.

     

    I have following doubts-

     

    Q1. The schema on which the dataset is built has 3 identities in total.. so identity type which is limited to 20, does that mean the maximum no of different identity namespaces coming from sources should be 20 max or is it the the number of identities of same identity namespace should be 20 max? 

     

    For example-

    Case 1: 20+ different identities from 20+ identity namespaces.

    Case 2: 20+ records from one or two identity namespace.

    Which one would be the correct interpretation of MaxIdentities error? 

     

    Q2. Above methods suggested by you is only possible before data lands in AEP, right? 

     

    Thanks,

    Sambit

      KumarRishii
      KumarRishii
      Level 5
      July 7, 2025
      Identity type limited to 20" means you can have at most 20 distinct identity namespaces/types. You can have many records/values per type, but only 20 different types/namespaces.
       
      Yes, the methods I suggested (identity cleanup, ECID validation, etc.) are all pre-ingestion solutions — meaning they need to be implemented before the data lands in AEP.

      I hope the above reference helps clarify your queries.

      Terms & ConditionsAccessibility statement

      Loading footer...