Share all details about your problem, including any error messages you may have received.
Hello all, I am trying to do a account group aggregation with pagination for one of my web service connector application. However, I am currently facing an issue when using the Paging tab.
Somehow my account group aggregation does not end. The task will keep running. I have checked on the api side that is it indeed returning a value for nextLink to decide if there are any more records to be retrieved.
I have a total of 70 records, and my page size is 50. Based on the CURL I did:
First iteration returns 50 records and nextLink != “”
Second iteration returns remaining 20 records and nextLink == “”
Would like to check how do I implement this correctly using the After Operation rule instead of the Paging tab?
Hi @shijingg, I have a few inquiries to help troubleshoot this:
1st: Did you try the pagination logic directly outside IdentityIQ — for example, using Postman or CURL?
– If yes, is it returning paginated results correctly with a valid nextLink logic?
– If you haven’t tested it externally yet, please give it a try and let us know the behaviour.
2nd: Temporarily disable the pagination logic inside IIQ (clear the Paging tab), then run the aggregation.
– Is the aggregation task complete?
– If it still loops or hangs, the issue is more likely with the aggregation task logic, not the paging.
3rd: If: The pagination works as expected in Postman, But the aggregation fails or loops even without pagination
– Then the problem is likely within the task logic or connector config itself.
However, if both the standalone API test and aggregation without pagination behave as expected, then the problem is likely with how IIQ is parsing or evaluating $response.nextLink$ in the Paging tab.
Why Pagination Might Not Work in Your Case:
$response.nextLink$ might not be resolving correctly because:
– It’s nested inside another JSON object, and the Paging tab doesn’t parse nested paths well.
– If nextLink == “”, IIQ might still build a new request with an empty link, restarting from page 1.
– String comparisons like == “” sometimes fail due to nulls or whitespace.
If it turns out to be a parsing issue in the Paging tab, I can help fix it with you — or you can shift the logic to an After Operation Rule where you’ll have full control.
Let me know what you find after these checks :), have a nice and great one!
