This would happen if you had a table with, let's say, 10 rows and you attempted to access row 11. If you are certain that your index exists within the table, then you'd need to provide more detail as that could mean that the table is getting loaded dynamically or some other issue that would likely need hands on support.
The index/key in question is index of a ForLoop that we have used to access rows of the target tablesection (TS).
The underlying table takes a lot of time to load, and I think that HTMLTableDesigner replica, i.e. TS would also take lot of time for creation and matching. The error occurs mostly when we have lot of records. So I think we are trying to search a record with an index, but the record for that index value is yet to be created.
To mitigate this possiblity, I have added a WaitForCreate for the TS before the ForLoop that accesses cells in it with a timeout of 1 min. Yet, we get the error which kind of undermines the above assessment.
Does WaitForCreate on Table sections return a true when the underlying table gets loaded, and not the table section? Or, is the above assessment wrong to begin with?
I had a similar problem - table data getting dynamically created, using forloop, error appearing when there are huge records and the iterations goes for hours. I tried adding a WaitForCreate for the dataCell of the table (similar to your WaitForCreate for TS), before trying to fetch the value from the dataCell. For the past two days, have not seen an issue and it seem torun perfectly - hoping it got resolved now. Looks like implicit WaitForCreate does not work for dataCell and need to be explicitly called.