Hello - I am trying to run scheduled Blue Prism automations on our production server. It has login agent installed on this system. I specified that the Scheduler should run my automations.
If I right-click on the schedule and choose "run now" (while I'm logged in to the Runtime Resource (RR)), it works fine.
When I log out and let the Scheduler try to run the automations, it fails to complete and I receive the exception "could not identify process owning the current foreground window".
We are using Blue Prism 6.2.1. I've gone over the user guide for Login Agent and did not see any steps we missed during installation (including checking security/system policies). I've watched the videos posted by BusyPing and didn't really see any thing the video showed that we are not doing.
From the Control Center, I can see my RR system with the "key icon" indicating Login Agent is running. Any ideas on what to check?
If I right-click on the schedule and choose "run now" (while I'm logged in to the Runtime Resource (RR)), it works fine.
When I log out and let the Scheduler try to run the automations, it fails to complete and I receive the exception "could not identify process owning the current foreground window".
We are using Blue Prism 6.2.1. I've gone over the user guide for Login Agent and did not see any steps we missed during installation (including checking security/system policies). I've watched the videos posted by BusyPing and didn't really see any thing the video showed that we are not doing.
From the Control Center, I can see my RR system with the "key icon" indicating Login Agent is running. Any ideas on what to check?