When you change the find logic of an element, then try to re-schedule the test list to run remotely, the updated Pages.g.cs file is not pushed to storage. The test list will use the old version of the Pages.g.cs file currently contained in storage which can cause coded steps to unexpectedly fail with "element not found" since it's using the old find logic.

A temporary work around is to update the date/time stamp of the settings.aiis file to be the current date/time. Once touched then the current version of the Pages.g.cs file will be uploaded to storage.