Hi @ksuneeth85
No—removing manuallyCorrelated only allows correlation to be recalculated; it does not detach the account.
With unoptimized aggregation, the account should be reassigned if the new logic finds another identity.
If no match exists, IIQ creates an orphan Identity Cube—it does not leave a Link identity-less.
Hi @ksuneeth85
If you’re curious about unlinking, you can try:
Identity Warehouse > Application Accounts tab > select the application > Delete > Save.
This unlinks the account from that specific application (it removes the Link). Then run aggregation again to see how it correlates.
Hello Suneeth. @bohorapujan’s approach should help here.
Changing the correlation logic and running an unoptimized aggregation forces IIQ to reprocess the account, but it does not mean the existing Link will simply be removed. If the updated correlation resolves to another identity, IIQ can perform a Correlate Reassign.
If your goal is to explicitly un-link the current account and test the new correlation from scratch, delete the Link from Identity Warehouse → Application Accounts, then run the aggregation again with Disable optimization of unchanged accounts enabled.
If it still correlates to the same identity, I would verify what the updated correlation logic is actually returning for that account.
changing the correlation logic does not automatically uncorrelate existing Links. In IIQ, every Link must belong to an Identity. If the account is reprocessed and no longer matches the original identity, IIQ typically correlates it to another matching identity or maintains/creates an uncorrelated (orphan) identity rather than leaving the Link unattached.
@ksuneeth85 It this issue still persists, please share your app xml, correlation rule and a sample identity on which wrong correlation is available.This will help us troubleshoot your issue better.