I’m working on a workflow in SailPoint Identity Security Cloud (ISC) and have run into the 100-item limitation of the Loop operator. My use case involves processing a list of items (identities, access items) that often exceeds 100—sometimes reaching 900 or more. According to the documentation, the Loop operator’s input array is capped at 100 items, and any excess causes the workflow to either fail or skip processing beyond that limit.
Loop Doc: https://documentation.sailpoint.com/saas/help/workflows/workflow-operators.html#loop
I’d love to hear how others in the community have approached this limitation. Specifically:
What strategies or workarounds have you used to handle lists >100 items in a workflow?
Any best practices for keeping this efficient and maintainable?
Could you please share the exact use case? In most situations where workflows have limitations, we can use scripting, like PowerShell, to achieve the desired outcome. However, these tasks typically require manual intervention.
The use case here is for example based on an attribute change that we are populating example lifecycle state we need to trigger a workflow that should get all identities remove all the access user is having.
Now the user here can have more than 100 access profiles tagged to it.
Thanks everyone for the feedback and suggestions so far! I really appreciate the ideas around removing access and other specific use cases. To clarify, my original question was a bit more general, I was hoping to hear from anyone who’ has tackled the Loop operator’s 100-item limitation in a workflow and could share a sample approach if they’ve successfully implemented.
In your case, if it’s looking at multiple identities, you can probably look at the asynchronous recursion. Try downloading the examples in this document and ply around with it for your use case.
