# Best Practices for Handling the Loop Operator’s 100-Item Limitation in Workflows

**URL:** <https://developer.sailpoint.com/discuss/t/best-practices-for-handling-the-loop-operator-s-100-item-limitation-in-workflows/103810>\
**Category:** SHF Discussion and Questions\
**Tags:** workflows, identity-security-cloud\
**Created:** [March 11, 2025, 4:15pm UTC](https://developer.sailpoint.com/discuss/t/best-practices-for-handling-the-loop-operator-s-100-item-limitation-in-workflows/103810 "2025-03-11T16:15:02Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![sidharth\_tarlapally](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/sidharth_tarlapally/32/26178_2.png) [@sidharth\_tarlapally](https://developer.sailpoint.com/discuss/u/sidharth_tarlapally)\
**Post date:** [March 11, 2025, 6:07pm UTC](https://developer.sailpoint.com/discuss/t/best-practices-for-handling-the-loop-operator-s-100-item-limitation-in-workflows/103810/5 "2025-03-11T18:07:19Z")

</div>

Hello @sameer1308

The following might help in resolving your query

> [@Workflow to remove ALL leavers' standing access](https://developer.sailpoint.com/discuss/t/workflow-to-remove-all-leavers-standing-access/13025):
>
> Hi everyone, This workflow auto-revokes any standing access leavers have either through a micro targeted access certifications or by leveraging revoke access requests after being terminated. This should ensure that all leavers’ access is removed upon terminated and not just access assigned through birthright roles. Additionally, an audit trail is generated to document when and why the access was removed. This workflow was designed and built with the help and input of a multiple people! Thank…

Thanks

---

_[View the full topic](https://developer.sailpoint.com/discuss/t/best-practices-for-handling-the-loop-operator-s-100-item-limitation-in-workflows/103810)._