Hi there,
While your current approach using Loop and Split tasks does technically work, it does have limitations—especially when it comes to visibility and manageability. As you've noted, the View Flow doesn't allow you to drill into individual loops, which can make operational tracking and auditing quite difficult.!--startfragment>

A more robust and scalable solution would be to use a multi-instance sub-workflow. This allows you to dynamically trigger a separate sub-workflow for each user task in your list. It not only improves visibility but also makes the process easier to manage and audit.

• If all user tasks are mandatory, configure the workflow to wait for all sub-workflows to complete before proceeding.
• If not all tasks are required, you can proceed without waiting for every path—just ensure you log responses appropriately so you can track outcomes and handle exceptions.

I've implemented this architecture myself and found it to be highly dynamic, auditable, and supportable. It's a tried-and-tested approach that scales well and simplifies maintenance.

Let me know if you'd like more details —happy to assist!

!--endfragment>

Thanks so much for the reply ​@sksrudra , great idea!