Is the AD aggregation you are referring account aggregation or group aggregation, also if it is account aggregation is promote managed attributes selected within the task definition
Also is this happening in both delta and Full aggregations?
@venkat_chaduvula
Can You try running On-Demand Aggregation of these groups ( if you have any On-Demand Job already) if not run Full group aggregation, also for these entitlements check what is the uncorrelated value in Database for these groups
you can check using below query
select uncorrelated,* from spt_managed_attribute, spt_application where spt_application.id=spt_managed_attribute.application
and spt_application.name='<Your AD App Name>' and spt_managed_attribute.value='<Your Value showing in Error>';
check the uncorrelated value, if this is marked as 1 - this might be causing the issue, check this value after running the Full Group aggregation once if it is still 1, we may have to look into your Group refresh rule and customization rules if any on your application and see why this is setting to 1 , if this value is 0 after Group Full aggregation you account aggregation should get fixed.
Which environment is this issue happening, lower or prod? or both?
Strange, if the groups are different daily, do you have any refresh rule or customization rule, if so can you please share, also Can you run the query to check if there any groups currently in DB
select uncorrelated,* from spt_managed_attribute, spt_application where spt_application.id=spt_managed_attribute.application
and spt_application.name='<your app name>'
and uncorrelated='1';
Is it possible to run the Account Full Aggregation again now and see if this is happening again with any group if so please share the managed attribute xmls samples of those groups and also can you share your customization and group refresh rules if any
It seems like you have native change detection enabled on the application together with promote manage attributes checkbox selected on the aggregation task.
You generaly can’t have both - and if you decide to use only one it should solve the problem.