The issue is with the Find Logic for the Search Result element in step 3. It likely does not have a unique identifier in the DOM, such as ID, and Test Studio crafted its Find Logic based on text content. So when you change the search query, the results are different and Test Studio can no longer find the element with a text content of "System".
There are a few ways to approach this. Ideally the search result element you intend to click has an ID, or some other static attribute, so that Test Studio can reliably find the element between iterations, no matter its text content.
However I suspect that it does not. In that case, you can data drive the find expression for the search result element to use the same data column that is bound to the search query step. This currently cannot be done through the UI. Here's how to do that in a coded step. Here is some code I adapted specifically to a search query and result scenario:
HtmlAnchor link = Find.ByContent<HtmlAnchor>(Data[
Be aware that if the search query data is not specific enough, the code above may locate and click a different link with matching content.Greetings,
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Public Issue Tracking
system and vote to affect the priority of the items