Has anyone faced issues in running attended automations with Windows 2019 or 2022 os versions. The UiPath bots fail immediately and logs show the error message : Error occurred : Cannot bring the target application in the foreground
- Session isn’t truly interactive (RDP minimized, locked, or multiple sessions active).
- App and UiPath Assistant running with different admin levels.
- Windows Server UI restrictions (no active display, secure desktop, UAC prompts).
- Using Foreground/Hardware Events input when the app isn’t visible.
- Orchestrator starting the job in a different session.
Welcome to the community
is it core..as it has a limitation of only background
Apart from that do you have any notifications at the time of running..Also to make sure publish a dummy process with only a log message or message box and check if it works
cheers
ideally attended automation is to be run from assitant
task schedular might be creating the issue here
also may I know if no user is triggering then why is it attended?
cheers
Using the task scheduler and trying to run this unattended is against the terms for the attended licence. You must stop immediately.
Here you can see it explained by a UiPath member of staff several years ago.
I also strongly urge everyone else in this topic, stop writing workarounds for these situations. You are indirectly, or directly advocating for people to break their licence terms.
The issue was happening due to application selectors being updated
- Session isn’t truly interactive (RDP minimized, locked, or multiple sessions active).