Recorded web test says 'object not found'
A previously recorded test that was working is now saying objects not found so this automation now doesn't work
Forum Discussion
This is actually not an unusual problem for recorded tests. If the state of the application at the time of playback is different than the state at recording, you will get failure messages like this. Common examples are if the identifying properties for object mapping are dynamic... that they were looking for "StringA" when now, at playback, it's actually "StringB".
As a general best practice, after you record a test case, you need to go back through any mappings created and make necessary modifications to account for dynamic identification factors.