Hello,
I am using StudioX 2022.4.6.
I am debugging a workflow using the Simulate input mode for NApplicationCard.
If I lock the screen using Win + L before running the debug on a Windows 10 machine, will it negatively affect the debugging?
While running any Ui automation, it is better to keep your system on and not locked.
Although Simulate method can work in background Ui automations may not work correctly under locked screen.
If you don’t have other option, you can try remote debugging on another VM (dev or any other) but for that you need to have a VM.
Hello @gorby
What should normally happen with Simulate
When using Simulate with NApplicationCard:
• UiPath sends commands directly to the application’s backend (UI frameworks like Chromium/Java, etc.).
• It does not depend on physical screens, mouse, or keyboard.
• Theoretically → it should work even if the screen is locked.
Pitfalls (places where issues may arise)
In actual workflows, not everything is simulated. If the process includes any of the following, locking the screen can impact debugging.
The likelihood of failure increases when locked.
• Activities that use hardware events
• Click / Type Into that Simulate does not actually support (some legacy applications)
• Image-based or OCR activities
• Element visibility checks (if they depend on rendering)
• Steps that require an active user session
There are also risks involved.
• Opening or attaching to an application during debugging
• Applications that pause or throttle when the session is locked
• Anything related to Windows UI focus
Hey, As you pointed out my workflow stopped even screen unlocked.