Hello, im using studio version 2025.0.175 STS. Im trying to run a simple process that use a "Use application/browser " activity to click around on a web page. I have downloaded the chromedriver and made an environment path variable and it can execute from anywhere. I have also installed the chrome browser. The process work with when i dont run it in headless mode but not when i set to headless in the activity under properties. Please help.
Hello @simon.zorde Make sure you selected Chrome in the Application Path or URL and not Edge or something else also your Chrome browser version must match the chromedriver version.
Cheers
It is chrome in application path and the driver matches the browser version. Says could not find user interface
Okay so try this
For every Click, Type Into, etc. set the property InputMode = Simulate because Hardware input modes do not work in headless sessions.
Also in properties goto Browser Options then Arguments and paste this
--headless=new --disable-gpu --window-size=1920,1080 --disable-dev-shm-usage --no-sandbox
Cheers
i have tried your suggestions but unfortunately it gives the same error
Type Into ‘INPUT forside-soegefelt…’: Could not find the user-interface (UI) element for this action.
Possible solutions:
• Ensure application is opened and the UI element is visible on the screen at execution time
• Edit the Target of the UI activity and use Validation to debug the issue.
• If needed, re-indicate the element as its properties might have changed
• Use “Check state” activity to check the application state before executing the action
• Increase the “Delay before” value to allow time to the application to render entirely and become responsive
[Target]: Strict selector failure:
The closest selector matches found are:
[69%] )
Did you set it up from scratch Simon?
There are some examples and tutorials around, and perhaps its worth following one and following their exact setup, using the same websites they show that work in headless mode.
I don’t have enough experience with headless browser automation, but it wouldnt surprise me if some sites dont work properly or at all, and so my train of thought is that you should isolate whether this is an issue with your setup, or an issue with the specific site. Doing what I suggest could narrow that down.
Can you share in which website you’re automating or using type into?
Yes ofcourse its: https://datacvr.virk.dk/
Yes ofcourse its: “https://datacvr.virk.dk/”
Okay it maybe due to some possibilities like
The element is inside an <iframe> or shadow DOM like selectors that work in normal mode often fail in headless unless you attach to the frame or adjust the selector.
Also I thin the page behaves differently in headless and also DOM never finishes loading before the Type Into runs.
CHeers
i doesn’t work on “https://rpachallenge.com/” either
weird that it is working for you and not me. im using chromedriver: 141.0.7390.54 and chrome version: 141.0.7390.55
Try adding a Delay before the Type Into Activity of 3 to 5 sec because sometime type into types but the page isn’t fully loaded in headless mode.
Cheers
You can try with classic activities for the same you want to perform like type into for that filter the activity panel with classic then you’ll get the classic activities try that and see if it works or not.
i got a couple of activities working with strict selector. It seems that the selectors are maybe different in headless mode, but im not sure. The other selectors still dont work
May I know that why are you trying to do this in Headless mode and is it commpulsory?
If it is not mandatory to do it in Headless mode then try that without headless mode as i think sometimes selectors changes in headless mode as per the compatibility.
Cheers