That looks like an error message that occurs when using UIA mode for an element. So, one thing to note is that what it means by "unable to match any windows" probably really means "unable to match any elements using UIA mode". I don't know if that helps at all, but it seemed worth mentioning.
If you're saying it works on the first row but not on subsequent, then app either hasn't returned to the starting page/screen/state before beginning the second row OR your app modeller element attributes aren't flexible enough to work with the subsequent rows. Could you screenshot or describe the app? And it would also be helpful to see the app modeller attributes you're using. Sort by the Match column so all the selected attributes show next to each other.
Another possibility here is that maybe you've designed everything perfectly and the only issue is a lack of a wait stage in your loop (assuming you have a loop somewhere). Ideally you'd use a conditional wait that waits for the target element to exist before trying to interact with it. It could be that between page loads, blue prism is trying to work with the element before it has reloaded in order to handle the second row.
It's hard for me to guess what scenario you are encountering without seeing the app or your element attributes.
------------------------------
Dave Morris
3Ci at Southern Company
Atlanta, GA
------------------------------
Dave Morris, 3Ci at Southern Company