@kevinwoodbury
Native change detection is different from Native Identity change event, I have clearly explained this in below thread
- I’m guessing these objects are created during aggregation of the Active Directory Connector? Currently our AD connector does not have Native Change Detection turned on, I’m curious as to how these are being generated.
Answer - these are generated because of feature checked Under Global settings Native Identity Change Event detection , check under Miscellaneous.
. I see a large volume of these objects are “stuck” in a state of “Waiting”. What process moves these from a status of “Waiting” to a status of “Processed”, additionally what actually happens in IIQ when these change from a status of “Waiting” to a status of “Processed”?
Active Directory ObjectGUID, move/rename support FAQ - Compass
Check the above thread, you will have detailed explanation, in short SailPoint changed the key for aggregation starting 8.3 causing this events if there is change in native identity on an account
Note - Please dont get confused with Native change detection with Native Identity change event, these two are completely independent