@narendranathanv

Here’s the thing: after you click a row and the page navigates, every clone you got from GetClones is destroyed, so the old ListLoop items are invalid and you see Component not listed. The fix is to never reuse clones across navigation when you return to the results page, first WaitForCreate on the table (and optionally check IsCreated/Ready), then call GetClones again to build a fresh list. Re-initialize the ListLoop on this new list (Initialize/Reset) before continuing. If you want to continue where you left off, save the current row index or a unique customer ID before you click, then skip already-processed items after you rebuild the list. Turn on UseKeys for the row/link controls and add a stable match rule (like customer ID text in the row) so the control rematches cleanly after navigation. Wrap the click in try/catch; on Component not listed, perform a quick rematch sequence: WaitForCreate(table) → GetClones → ListLoop.Initialize, then retry. Add short waits after submit/return so you don’t read a half-rendered table. Best practice: first collect all customer IDs into a simple string collection, iterate that list, and open each record by ID—this avoids depending on fragile clones altogether.