It refers to the GlobalVariable.chromeDriverPath. This implies that @vasavi.00 uses a custom path for ChromeDriver, which could be different from the one bundled in Katalon Studio and managed by “Update WebDriver” tool.
I doubt it. I suspect that the version of ChromeDriver stored at the GlobalVariable.chromeDriverPath is possibly not 143.0.7499.42.
Are you launching with your own chrome profile? If so, make sure your existing chrome browser is closed. Chrome does not allow you to launch from the same directory twice.
If you want to use a chrome profile and keep your existing browser open, try creating a new profile in a different directory, specifically for automation use.
The “Response code 500: session not created: DevToolsActivePort file doesn’t exist” error usually means ChromeDriver cannot start or attach to a Chrome instance, most often because of version mismatch or profile/port conflicts.
Main causes
ChromeDriver version at GlobalVariable.chromeDriverPath does not match the installed Chrome browser version, even if you believe it is 143.0.7499.42.
Multiple ChromeDriver processes or Chrome instances are already running and blocking startup.
A custom Chrome profile directory is reused while Chrome is already open using the same directory.
Fix steps
Kill any stray ChromeDriver processes
From CMD:
bash
taskkill /F /IM chromedriver.exe /T
Then rerun the Katalon test.
Ensure ChromeDriver exactly matches Chrome
In Katalon, use Tools → Update WebDrivers → Chrome to sync the bundled driver to your Chrome version.
If you override with GlobalVariable.chromeDriverPath, verify that file is the same driver version as shown in the Chrome “About” dialog and the Katalon “Update WebDriver” tool.
Check custom Chrome profile usage
If you pass a user-data-dir or custom profile directory via Chrome options, close all normal Chrome windows before running, or point automation to a separate, dedicated profile directory.
Inspect Chrome debug logs if it persists
Enable Chrome debug logs as per Google’s guide and review them for more specific startup failures (permissions, invalid flags, bad profile path, etc.)
It is nonsense to say this. Google Chrome tends to change its internal without notice. Users are supposed to accept ANY changes. You need to be prepared.
Thank you for your response. Yes, we are aware that Google frequently updates Chrome, which is why we always update the ChromeDriver and also update the drivers in Katalon. What I meant to say is that the code was working earlier, but now we are facing issues.