@SudR5222I have not encountered this specific issue myself. I do know however that key fittings can be fickle. I delete the instance of the partial screen from the automation and re-add it. This should trigger Studio to recalculate the upstream key and allow you to select Index again and connect it to your loop.

If this doesn't work, the next thing I would try would be to recreate this automation (or even a simpler one) from scratch just to confirm that you can access any data from partial screens. To do this, I would simply create a blank automation that accepts an integer (which would be your index) and then gets the text property of the partial screen and returns it to an exit point. You can then test this during interrogation to see if it works there.

If that is also failing, I would open a support request, as the getting hands-on with your application would be necessary at that point.