ContributionsMost RecentMost LikesSolutionsExported tests failing - Object was not found Hello All I created a suite of test objects for some software that all work fine. I have exported these and imported them into a new Project Suite as this is a significant revision and felt it would be best to make a new suite, but when I try to run the tests I just get exceptions stating The "Object Name" object was not found. All of the objects seem to have been given parentheses during the exporting process, so they all look like Aliases.First().Second().Third(). However when I record the tests again, they are exactly the same without the parentheses. Does anyone know how I can solve this, rather than record hundreds of tests again? Thanks SolvedRe: Consistency in play back Thanks for the replies. I have placed a few if object not available statements in a few of the more troublesome scripts and they seem to be more stable. I have also added timers to test the lengths of each test to see if it is indeed the software running too slow. Consistency in play back Hello all I did try to search and look around the internet, but I couldn't find anything obviously relating or a solution to my problem. The issue is I have created a test made from several keyword tests which runs fine, but if I run it several times, eventually it breaks in what looks to be the same place every time. The first time it ran 150+ times before stopping, but after trying to fix the issue I have seen it fail on run 29 and later at 50. the script in question clicks a check box, then clicks a button before moving to the next keyword test. First it failed to click the check box because it wasn't there, so I put delays at the start and then between clicking the check box and button, but still it struggles. I have an error condition so if there is an issue and the software is not where it should be at the end of the test, it restarts the software ready for the next cycle, however it just ends and goes to the summary screen. However the playback properties stop on error and stop on warning are both disabled so it should work. Does anyone know how to make the button clicking more consistent or how to make the test cycle on error? Thanks