I am getting error "Web element was found but not clickable"

Description:

Most probable reasons for getting "Web element was found but not clickable" error message are:

1. User is not replicating correct behavior through blocks in automation flow.
2. The element is there in HTML DOM but not available for interaction, e.g. the browser is still loading or it may be hidden (not visible).
3. The element is clickable but there is a spinner/overlay on top of it.

Lets try to understand the first issue by an example in LEAPWORK:

• User opens amazon.com
• and capture "Echo & Alexa" from "Departments" drop down (without hovering/expanding department)
• Run test
• Above test will failed with "Web element was found but not clickable" error message

Please observe, that test started and amazon.com was opened but user did not add a block for hovering on  “Departments” drop-down to expand it and still tried to click on "Echo & Alexa" link which was hidden behind in HTML. So, the element was there in the HTML structure but it was not clickable as drop-down was not expanded (below screenshot shows correct point to click before clicking "Echo & Alexa" link).  

Please try to look at studio.log file to get more details about error message, path of log files is: C:\Program Files\LEAPTEST\Logs\studio.log.

Resolution:

Below are the ways to handle above mentioned scenarios: 

Scenario 1:  User is not replicating correct behavior through blocks in automation flow.

Resolution 1: To solve this user should try to replicate the same behavior in flow as a manual tester will do example shown below 

Scenario 2:The element is there in HTML DOM but not available for interaction, e.g. the browser is still loading or it may be hidden (not visible).

Resolution 2:In this situation element usually take time to load properly, user should use "Await DOM change" feature in blocks to handle this synchronization challenge  

Scenario 3: The element is clickable but there is a spinner/overlay on top of it.

Resolution 3: Try to check condition, if spinner/overlay is displayed then wait else move ahead (click Await not found checkbox) and then use click web element block. 

 For any clarification, please contact our Priority Support.