# Production AZURE AD aggregation delay **URL:** \ **Category:** IIQ Discussion and Questions\ **Tags:** connectors, aggregation, identityiq, sailpoint-identity-security\ **Created:** [September 9, 2026, 4:23am UTC](https://developer.sailpoint.com/discuss/t/production-azure-ad-aggregation-delay/221966 "2026-09-09T04:23:27Z")\ **Posts on this page:** 1\ **Showing post:** 15
**Author:** ![lalithajay](https://avatars.discourse-cdn.com/v4/letter/l/96bed5/32.png) [@lalithajay](https://developer.sailpoint.com/discuss/u/lalithajay)\ **Post date:** [September 15, 2026, 6:51am UTC](https://developer.sailpoint.com/discuss/t/production-azure-ad-aggregation-delay/221966/15 "2026-09-15T06:51:32Z")
Hi Neelmadhav, Thanks for your reply. Considering we have ISC , would you be able to provide us with some specific steps to try, including where we should look to identify and clear the bottleneck? Were you able to overcome this issue in your testing? If so, could you please share the steps or configuration changes you carried out to resolve it? I’m also wondering whether the post below could be related to the same issue. Could you please have a look and let us know your thoughts? > [@Stuck aggregation tasks - Monitoring](https://developer.sailpoint.com/discuss/t/stuck-aggregation-tasks-monitoring/137811/2): > > HI @vinnysail You’re correct that IdentityIQ doesn’t have a fully “built-in” automated detection and recovery mechanism for this specific scenario. The TaskResult object’s status changing to Failed or Terminated is the primary built-in indicator, but in your case, it remains Running Your approach of monitoring long-running tasks via a scheduled rule is a good starting point and a common practice. Let’s delve deeper into potential causes and more robust detection/recovery strategies. Understan… --- _[View the full topic](https://developer.sailpoint.com/discuss/t/production-azure-ad-aggregation-delay/221966)._