Most of the users face the issue where their flow fails due to the reason "WebElement not found".There are three possible reasons due to which it happens:
Scenario: User want to open an e-commerce website and in his/her flow used "Get Web Text" block to capture the text, in that block by default the Timeout(sec) is 10 seconds. But when the user runs his/her due to insufficient timeout LEAPWORK application won't be able to capture the text which results in the failure of the flow like shown in the image below:
The maximum time spent in searching for the captured web element before triggering “Not found” is 10 seconds.
Note: All cases have a “global timeout” that can be configured in the “Settings” panel. This is unrelated to the timeout of a single building block. However, a running case will automatically be canceled if it runs for longer than the global timeout.
Page Loading in progress:
Delay the search for the web element until there have been no changes to the page’s DOM for a specific period of time — for instance, 3 seconds.
- Locator Strategy:
Sometime the element captured will not work during run-time execution due to incorrect locator strategy. To Resolve this you need to re-validate the strategy and then save it.
For any clarification, please contact our Priority Support.