I am testing a custom scenario to check SMAX users via MaaS connector for their existence in another repository (xml files exported from another datasource), in order to automated their deletion (change to contact) and sync with this repository.

I noticed if I use the data generator to query MaaS, SMAX will only let me work with at most 250 users at a time, and bulk update 100 at a time, but there are ~18K users. So, I have the MaaS connector mapping loop back on itself, check the [meta.total_count] in order to dynamically generate parameters with "skip=" and "size=100", so that users are queried in Person collections of 100 at a time. It also checks to ignore the doc if the total has been reached, to avoid infinite loop.

However, this method keeps the previous loop iteration of the produced docs as parents, including all ancestors, and it only gets to about 5000 users before it starts throwing warnings about "maximum linked parent documents reached...your scenario may contain an infinite loop".

I could ignore this warning, but if running unsupervised, I want to be alerted to other warnings, so don't want to ignore warning threshold on connect-it alert.

Is there a better way to accomplish this? Otherwise, the MaaS connector just seems to query the first 250 users in a Person collection if I query for all users, and then stops, so it doesn't seem to have any built in capability to auto-process paged results like this.