Share all details about your problem, including any error messages you may have received.
We have a rule that if an account cannot correlate, it creates/correlates the accounts to a generic “app name uncorrelated accounts” identity. Recently we had an app that went through 787 uncorrelated accounts and removed them from the system. From the UI/Identity Warehouse page everything looks good but in the debug page/review, we are seeing 787 still there.
Has anyone run into the discrepancy in UI vs Object itself? I think the solution is deleting the identity and letting it rebuild but need to have an answer for why it potentially happened.
it could happend when there is any item linked to the identity like IdentityRequest.
Please check in debug if there are any IdentityRequests open for that identity.
Did you remove those Links from the Application?
Or did you remove the Identities?
If you only removed Accounts, it would not have deleted the Identities. Accounts and Links are not the same.
If you removed Accounts, all associated Link objects would have been deleted.
However, Identities must be removed manually.
How we have it configured is if you don’t match correlation value to an identity, we add that account from the application to an uncorrelated bucket. The 787 links existed on the identity at one point but since have been removed from the application. After being removed from the file we ran a full aggregation and it said it deleted 787 but the links still exist on the object in the debug page. Just not the UI. I figured this was a weird bug since 787 links is a lot from a performance standpoint but wasn’t sure if this is known.