Expand my Community achievements bar.

Help shape the future of AI assistance by participating in this quick card sorting activity. Your input will help create a more effective system that better serves your needs and those of your colleagues.
SOLVED

1 records as they had only one identity per xdm record

Avatar

Level 9

Hi All,

I am getting this  skipped 1 records as they had only one identity per xdm record from Identity Graph. Basically I have 1 Experience Profile with two differents Dataset and 1 Experience Event.

Can you help me to understand better whats DOES skipped 1 records as they had only one identity per xdm record mean?

Thanks

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

@Luca_Lattarini did you check this - https://experienceleague.adobe.com/docs/experience-platform/identity/troubleshooting-guide.html%3Fla...

Identity Service only links identities when single records present two or more identity values. This error message occurs once for each ingested batch, and displays the number of records where only one identity could be found and resulted in no change to the identity graph.

 

For Id Graph to work right it needs min of 2 ids - if a record has only one id that's where its skipping to be shown on id graph. That doesn't mean record is not ingested in UPS - its just not shown in Id graph.

In AEP remember we have different storage, this process failed to update the Id graph since it has only one Id.

- Data Lake

- Unified Profile Store (UPS)

- Identity Graph 

- Edge storage

View solution in original post

2 Replies

Avatar

Correct answer by
Community Advisor

@Luca_Lattarini did you check this - https://experienceleague.adobe.com/docs/experience-platform/identity/troubleshooting-guide.html%3Fla...

Identity Service only links identities when single records present two or more identity values. This error message occurs once for each ingested batch, and displays the number of records where only one identity could be found and resulted in no change to the identity graph.

 

For Id Graph to work right it needs min of 2 ids - if a record has only one id that's where its skipping to be shown on id graph. That doesn't mean record is not ingested in UPS - its just not shown in Id graph.

In AEP remember we have different storage, this process failed to update the Id graph since it has only one Id.

- Data Lake

- Unified Profile Store (UPS)

- Identity Graph 

- Edge storage

Avatar

Employee

@Luca_Lattarini : Single node graphs are currently not stored in the Identity Graph.Hence you see the message that it has been skipped from Identity Service.