Hi shippee and varada, You have to distinguish between synchronization which detects when an action is finished (browser is idle) (1) and the synchronization for finding an element on the web page (e.g. button) (2) . For (1) "Synchronization Timeout the default is 5 minutes and should never be reached it's just a measure of last resort if there is any problem with synching (the webapp issues requests forever and SP cannot decide when it is finished). Usually the synch should work out of the box and this timeout should not be relevant. We just want to avoid to wait forever, just in case. The timeout for (2) ( "Object Resolve Timeout") default 5 seconds , the sychronization for finding objects is more relevant. Sometimes, for example, loading the page or doing some action in the browser window is finished but the UI element is still not visible for some reason. So SP waits (5 seconds by default) until the UI element is visible. Example API call: BrowserClick("//BUTTON") First SP tries to find the element with the locator "//BUTTON" (see doc for details on locators). If it was not found within the 5 seconds timeout the error "UI element not found" is issued. If it was found the mouse click is performed on the found element. For some edge cases the synchronization for when actions are finished (1) is not perfect. So it might be that the synchronization detects "idleness" of the browser too early and executes the next action (maybe BrowserClick()) too early. So in this case the 5 seconds timeout might be to short. I hope I could clarify this topic a bit. Regards, Philip
↧