Account aggregtion failures for multiple connectors

Identity Security Cloud (ISC) ISC Discussion and Questions
1

Hello,

I am facing the aggregation failures for multiple connectors like AD, Entra ID and getting the below error. The test connection is successful.
I have restarted the VA cluster also but it did not help.

Could you please help

2026-04-20_22h06_17
2026-04-20_22h06_17547×248 6.93 KB

:bangbang: Please be sure you’ve read the docs and API specs before asking for help. Also, please be sure you’ve searched the forum for your answer before you create a new topic.

Please consider addressing the following when creating your topic:

  • What have you tried?
  • What errors did you face (share screenshots)?
  • Share the details of your efforts (code / search query, workflow json etc.)?
  • What is the result you are getting and what were you expecting?
2

@maninderkaur_co-op Is it failing for all types of connectors or a specific type of connector ?

3

It is failing for all connectors which are using VA cluster. Example AD, Entra ID and One Scim 2.0 based connector

4

What is the error that you are getting in VA Cluster?

5

Hi Maninder,

Since this is impacting all connectors using the VA cluster (AD, Entra ID, SCIM), the issue is most likely at the VA level rather than with individual sources in SailPoint Identity Security Cloud.

A few things you may want to check:

  • VA logs: Look for errors in ccg.log and va.log around the aggregation time

  • Connector Gateway status: Ensure all VA services are up and stable (no restarts/crashes)

  • Network/DNS: Even if test connection works, aggregation may fail due to intermittent DNS or firewall issues

  • Certificates: Check if there are any expired/changed certs affecting connector communication

  • VA version: Make sure your VA is on a supported/latest version

Since test connection is successful but aggregation fails, it usually points to:

  • Execution timeout

  • Authentication/token issues during aggregation

  • VA resource constraints (CPU/memory)

Also, as Manish mentioned, it would really help if you can share the exact error from the VA logs — that will make it easier to pinpoint the root cause.

6

Can you share the error you are getting in VA cluster?

7

Thank you all.
It is resolved and was happening due to a latest CCG version having which was having some issues and VA has been pointed now to another CCG version by Sailpoint.

8

Glad it was resolved. Thanks for the update