[Replace this text with your version of IIQ. The more specific you can be (7.1, 8.3, 8.X), the more people can help. If you do not know, put Unsure.]
8.4
Please share any images or screenshots, if relevant.
[Please insert images here, otherwise delete this section]
Please share any other relevant files that may be required (for example, logs).
[Please insert files here, otherwise delete this section]
Share all details about your problem, including any error messages you may have received.
[Replace this text with the problem that you are facing]
We have integrated the web service application with SailPoint and configured the Account Aggregation operation. However, the WS application does not support pagination. When the aggregation API is triggered via Postman, it returns a 200 response code after a delay of around 60 seconds and includes the complete response with data.
In SailPoint, the Account Aggregation task completes as soon as the 200 response is received. At that point, the response appears empty, and no account records are being fetched into SailPoint. However, when printing the rawResponseObject from the After Web Operation rule, it shows that 20k records are actually present.
We need guidance on how to delay the completion of the aggregation task until the full response is received, or any alternate approach to fetch all accounts despite the lack of pagination support.
I can confirm that the issue is not related to schema mapping, as single account aggregation is working correctly using the same schema configuration.
Additionally, we are able to successfully fetch accounts when the application contains between 500 to 1,000 records.
From my observation, when triggering the Account Aggregation API via Postman, the API returns a 200 response code immediately, but the response body is initially empty. The actual response body with data is returned only after approximately 60 seconds due to huge records.
Please check the mapping.
This is the normal behavior when a response return a lot of records. The response is only one when you can see the Response Code and the body that contains the data and you see the date later 1 minute because postman or IIQ needs time to elaborate the information, but those comes all together.
Also, if you can see the accounts where receive 500/1000 elements and you dont see nothing when you receive 20k elements, I think the problem is on size of the data that you receive or thare are some element that broken something.
If you can filter, you can try to create some endpoint for aggregation where you read different subset of the accounts. Can you try this way?
