ContributionsMost RecentMost LikesSolutionsRe: The object "Sys" does not exist Thank you for your reply. Unfortunately it does not address the question. I know how to handle object missing errors, that's fairly trivial. The problem is I get a Sys object missing when I map a simple button object and add it to the NameMapping object and I want to know why. The object "Sys" does not exist Hi, I have developed a simple keyword test that is working except for one line. It is clicking a Yes button on a window dialog rather than the No button. So I changed the test to click the No button. I had to map the No button in the NameMapping object and save the change. When the test is rerun I keep getting the following If I restore the original NameMapping object without the newly mapped No button everything goes back to working. Now I know the process LabWare-prePROD exists because the immediate prior message is because of the below script code Set p = Sys.WaitProcess(processName) While not p.Exists Call Log.Message("Waiting for " + processName + " to start", "", pmNormal, logAttributes) Set p = Sys.WaitProcess(processName) Wend Call Log.Message(processName + " exists", "", pmNormal, logAttributes) What would make the Sys object not found? regards Solved