We have an automatized test framework that runs using Jenkins. The problem is when I run Jenkins as a service, we have some tests that are failing. We are testing a web application, and the test wants to write an email address ([email protected]) in an input field, but when if Jenkins runs as a service, the test won’t write the @ character and will fail because of validation errors (testtest.com). If I run Jenkins from cmd the test will pass. I tried with selenium grid, but same problem. If grid is run from cmd tests will pass. If i start grid from task scheduler, so I can have it running when the server is turned on, the test will fail. I understand that service and task scheduler commands will run is Session 0 isolated, but I don’t understand what could be different. Do you have any ideas?
I don’t think it is an encoding problem, because the test will write all characters with diacretics like éáőúöü, etc.
Browser: Google Chrome in headless mode.

Tried Jenkins as a service with local user, domain user, different encodings, different keyboard languages.
Installed Selenium Grid which runs okay if I start it from cmd, but as soon as I add it to task scheduler, to have it running when server starts, same happens.