Does the step use a data driven find expression? If so, you may need to alter the find logic in your data source. If not, this issue is likely caused by timing. You may experience intermittent find element timeouts when page load times vary across test executions or iterations. Because non-coded steps incorporate a built-in wait condition for the target element, ensure your test steps use ample timeouts. Please let us know if we can assist you further.
the Telerik team
Are you enjoying Test Studio? We’d appreciate your vote in the ATI automation awards.