@JettyRo @nnakirikanti  The _id value should be already unique per each event so i'm not sure that would be the case. Could you share your query logic?

Hi @JettyRo  There potentially may be a delay between the ingestion and when the counts would match up. In the UI, you are checking in the monitoring section, correct? Also, about how long has it been since the data was ingested?

Hello @sarahalamome  Maybe a silly solution, but have you tried to clear your cache and cookies and try this again? 

Sorry @Pradeep-Jaiswal I’m not very familiar with this then I’m afraid. I do see here that the refresh token will not always be provided.   Once you have fetched the access tokens for a user you may also be provided a refresh token in the response. A refresh token is only presented when the offline_...

Hi @Pradeep-Jaiswal  That is the same POST call I would make to retrieve a new token. Do you have your post script set as this below? var data = JSON.parse(responseBody); if (data.access_token) {     pm.environment.set("ACCESS_TOKEN", data.access_token); } else {     console.log("Unable to acquire...

Congratulations everyone! I'm very honored to be a part of this community and I learn something new from you all everyday!

@shubham10  For that specific profile's identity graph, are there more than 50 identities associated with it by chance?

Hi @shubham10  Trying to understand better here.. Did you ingest a gender value of "Male" and "Female" for the same identity value, at the same timestamp? I know that this can potentially cause issues when ingested at the exact same time.

@MeenalBo2 can't seem to find any info about how on-demand evaluations are affected. @brekrut thinking you may have more experience with this one, if you could help out?

Hi @MeenalBo2  I don't have an answer to your first question, but the 2nd, data distiller audiences should be evaluated the same as others either Batch, Streaming, or Edge