# Element Not Interactable Exception - Katalon Can't click my button?

**URL:** <https://forum.katalon.com/t/element-not-interactable-exception-katalon-cant-click-my-button/190334>\
**Category:** Web Testing\
**Created:** [April 23, 2026, 3:21pm UTC](https://forum.katalon.com/t/element-not-interactable-exception-katalon-cant-click-my-button/190334 "2026-04-23T15:21:17Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![rschuster](https://dub1.discourse-cdn.com/katalon/user_avatar/forum.katalon.com/rschuster/32/33814_2.png) [@rschuster](https://forum.katalon.com/u/rschuster)\
**Post date:** [April 23, 2026, 3:21pm UTC](https://forum.katalon.com/t/element-not-interactable-exception-katalon-cant-click-my-button/190334/1 "2026-04-23T15:21:18Z")

</div>

I’m trying to automate a loan application form, and I’m stuck on the very last step. The **“Submit Loan”** button is right there—I can see it perfectly fine on the page, it’s not hidden, and I don’t even have to scroll to find it.

But every time I run my script, it waits for a few seconds and then crashes with `Element Not Interactable Exception`. I tried using `WebUI.waitFor ElementVisible`, and the test passes that step, but as soon as it hits `WebUI.click`, it fails. I even tried adding a `WebUI.delay(5)` just to make sure the page was finished loading, but it still says it can’t interact with it.

---

<div class="post-metadata">

**Author:** ![qurzunta.kaab](https://dub1.discourse-cdn.com/katalon/user_avatar/forum.katalon.com/qurzunta.kaab/32/31470_2.png) [@qurzunta.kaab](https://forum.katalon.com/u/qurzunta.kaab)\
**Post date:** [April 23, 2026, 3:27pm UTC](https://forum.katalon.com/t/element-not-interactable-exception-katalon-cant-click-my-button/190334/2 "2026-04-23T15:27:06Z")

</div>

This usually happens for three reasons:

1. **Overlay/Shield:** An invisible “loading” overlay or a transparent div is still sitting on top of the button.

2. **Animation Lag:** The button is fading in or sliding, and the WebDriver tries to click the exact coordinates before the animation finishes.

3. **Overlapping Elements:** The theme uses a custom wrapper that consumes the click event instead of the button itself.

### **The Solution: JavaScript Injection**

When the standard Selenium `click()` (which `WebUI.click` uses) fails due to technical obstructions, the industry standard is to use a **JavaScript Click**. This bypasses the UI “physics” engine of the browser and sends the click command directly to the DOM element.

### **Custom Keyword Helper**

I’ve drafted a custom keyword that combines a “Wait” strategy with a JavaScript click to ensure the button is pressed regardless of overlays or animation states.

Groovy

```auto
import com.kms.katalon.core.annotation.Keyword
import com.kms.katalon.core.testobject.TestObject
import com.kms.katalon.core.webui.common.WebUiCommonHelper
import com.kms.katalon.core.webui.keyword.WebUiBuiltInKeywords as WebUI
import org.openqa.selenium.WebElement
import org.openqa.selenium.JavascriptExecutor
import com.kms.katalon.core.webui.driver.DriverFactory

class ActionHelper {

    /**
     * Force clicks an element using JavaScript to bypass ElementNotInteractableException
     * @param to The Test Object to click
     */
    @Keyword
    def forceClick(TestObject to) {
        try {
            // 1. Wait for it to be present in the DOM
            WebUI.waitForElementPresent(to, 5)
            
            // 2. Convert TestObject to a real Selenium WebElement
            WebElement element = WebUiCommonHelper.findWebElement(to, 5)
            
            // 3. Use JavascriptExecutor to trigger the click event directly
            JavascriptExecutor executor = (JavascriptExecutor) DriverFactory.getWebDriver()
            executor.executeScript("arguments[0].click();", element)
            
            println "Successfully force-clicked the element."
        } catch (Exception e) {
            WebUI.markFailed("Could not click the element: " + e.getMessage())
        }
    }
}

```

### **How to use it in your Script:**

Replace your failing `WebUI.click` with this: `CustomKeywords.'ActionHelper.forceClick'(findTestObject('Object Repository/Submit_Loan_Btn'))`

---

<div class="post-metadata">

**Author:** ![qurzunta.kaab](https://dub1.discourse-cdn.com/katalon/user_avatar/forum.katalon.com/qurzunta.kaab/32/31470_2.png) [@qurzunta.kaab](https://forum.katalon.com/u/qurzunta.kaab)\
**Post date:** [April 23, 2026, 3:38pm UTC](https://forum.katalon.com/t/element-not-interactable-exception-katalon-cant-click-my-button/190334/3 "2026-04-23T15:38:06Z")

</div>

also you can check this out [Katalon can't "see" my button inside a Web Component! - #7 by qurzunta.kaab](https://forum.katalon.com/t/katalon-cant-see-my-button-inside-a-web-component/190073/7?u=qurzunta.kaab)

---

<div class="post-metadata">

**Author:** ![arvind.choudhary](https://dub1.discourse-cdn.com/katalon/user_avatar/forum.katalon.com/arvind.choudhary/32/33165_2.png) [@arvind.choudhary](https://forum.katalon.com/u/arvind.choudhary)\
**Post date:** [April 23, 2026, 4:15pm UTC](https://forum.katalon.com/t/element-not-interactable-exception-katalon-cant-click-my-button/190334/4 "2026-04-23T16:15:52Z")

</div>

1. Try wait for element clickable  
WebUI.waitForElementClickable(findTestObject(‘path/to/SubmitLoanButton’), 10)  
WebUI.click(findTestObject(‘path/to/SubmitLoanButton’))

2. If Katalon’s normal `click()` still fails, you can trigger the click via JS:  
WebUI.executeJavaScript(“arguments[0].click();”, Arrays.asList(findTestObject(‘path/to/SubmitLoanButton’)))

If both above 2 don’t work then verify iFrame or Shadow DOM

---

<div class="post-metadata">

**Author:** ![depapp](https://dub1.discourse-cdn.com/katalon/user_avatar/forum.katalon.com/depapp/32/29178_2.png) [@depapp](https://forum.katalon.com/u/depapp)\
**Post date:** [April 24, 2026, 1:08am UTC](https://forum.katalon.com/t/element-not-interactable-exception-katalon-cant-click-my-button/190334/5 "2026-04-24T01:08:06Z")

</div>

hi @rschuster

first, swap `waitForElementVisible` for `waitForElementClickable`. Visible just means it’s rendered; clickable means WebDriver can actually interact with it, which is a higher bar. If that still times out, something is blocking the interaction.

open DevTools and inspect the button right before the click. Look for a transparent overlay, a loading spinner div, or a modal backdrop sitting on top of it. If you find one, wait for that blocker to disappear instead of using a blind delay.

if there’s genuinely no overlay and the element just won’t cooperate, use a JavaScript click as a workaround:

```groovy
WebUI.waitForElementPresent(findTestObject('Submit_Loan_Btn'), 10)
WebUI.executeJavaScript("arguments[0].click();", Arrays.asList(findTestObject('Submit_Loan_Btn')))

```

the JS click bypasses the browser’s interactability checks, so it works when the standard click cannot. Just know it also bypasses real user simulation, so use it only when the standard click is impossible.

---

<div class="post-metadata">

**Author:** ![dineshh](https://dub1.discourse-cdn.com/katalon/user_avatar/forum.katalon.com/dineshh/32/24488_2.png) [@dineshh](https://forum.katalon.com/u/dineshh)\
**Post date:** [April 24, 2026, 9:03am UTC](https://forum.katalon.com/t/element-not-interactable-exception-katalon-cant-click-my-button/190334/6 "2026-04-24T09:03:53Z")

</div>

**“Element Not Interactable”** = overlay/animation blocks Selenium click—use **JavaScript click** bypass.

## Quick Inline Fix

```auto
WebElement element = WebUiCommonHelper.findWebElement(findTestObject('Submit_Loan_Btn'), 10)
WebUI.executeJavaScript('arguments[0].click();', Arrays.asList(element))

```

**Waits + JS = 100% success** on loan forms.

## Keyword (Reusable)

```auto
@Keyword
void jsClick(TestObject to) {
    WebElement el = WebUiCommonHelper.findWebElement(to, 10)
    ((JavascriptExecutor)DriverFactory.getWebDriver()).executeScript('arguments[0].click()', el)
}

```

**Replace** : `WebUI.click(btn)` → `CustomKeywords.jsClick(btn)`

**Root Causes** : Loading spinner, z-index overlay, CSS transition. JS ignores all.

---

<div class="post-metadata">

**Author:** ![kazurayam](https://dub1.discourse-cdn.com/katalon/user_avatar/forum.katalon.com/kazurayam/32/333_2.png) [@kazurayam](https://forum.katalon.com/u/kazurayam)\
**Post date:** [April 24, 2026, 9:47am UTC](https://forum.katalon.com/t/element-not-interactable-exception-katalon-cant-click-my-button/190334/7 "2026-04-24T09:47:00Z")

</div>

WebUI.enhancedClick keyword would be helpful

> [@\[Trouble Shooting 101\] Element Not Visible Exception](https://forum.katalon.com/t/trouble-shooting-101-element-not-visible-exception/187100/6):
>
> @akshay_sartabe You should use [WebUI.enhancedClick](https://docs.katalon.com/katalon-studio/keywords/keyword-description-in-katalon-studio/web-ui-keywords/webui-enhanced-click) instead of WebUI.click. WebUI.enchancedClick internally always waits for the target element. See the following source code of the WebUI.enhancedClick keyword: package com.kms.katalon.core.webui.keyword.builtin import java.text.MessageFormat import java.time.Duration import org.openqa.selenium.JavascriptExecutor import org.openqa.selenium.WebDriver import org.openqa.selenium.WebElement import org.openqa.selenium.interactions.Actions import o…
