Hello everyone,
I've recently gotten into a new role for a company that uses the Blue Prism Login Agent. I did read the guides to understand how it works, however I still have some questions.
Context: We have a process. let's call it DumbSchedule process, that must run continuously all day so that we don't miss SLAs (I know this is not ideal and I am planning ways to get around this, however I must play with the cards I am dealt for now). Furthermore the logging in and logging out is not part of the process. Not sure if this is a best practice or not, however this does limit the use of resource pools, so another plan of mine, going forward, will be to include the logging in and out the machines in the process. This means in the scheduler the scheduler runs every 5 minutes. We are using Blue Prism Interact to load the queue, so the scheduler is set up like this
1. Login (Login Agent Process)
2. Process (Which can be a few seconds if there's no item)
3. Logout (Login Agent Process)
Now here is the problem. This schedule is setup similarly for many of our processes. This process, DumbSchedule, has it's runtime resource go offline at random times. The machine is not offline however the Automate.exe is not running (double checked by logging into the runtime resource and investigating). We also recently installed Dynatrace on some of our runtime resources to identify possible issues in our virtual environment. I noticed that the Automate.exe gets launched multiple times a day.
Through my previous work experiences we did not use a login agent, so the automate.exe file would only have to be launched once at bootup. Here it seems like it is launched multiple times. This leads me to some questions:
- Is this a best practice to launch it at login in every time? I googled the issue and from this thread it seems like it.
- Does logging off kill/close the Automate.exe? I don't see it in the object code, nor mentioned anywhere else, but I am not sure why the Automate.exe would not be running.
I've recently gotten into a new role for a company that uses the Blue Prism Login Agent. I did read the guides to understand how it works, however I still have some questions.
Context: We have a process. let's call it DumbSchedule process, that must run continuously all day so that we don't miss SLAs (I know this is not ideal and I am planning ways to get around this, however I must play with the cards I am dealt for now). Furthermore the logging in and logging out is not part of the process. Not sure if this is a best practice or not, however this does limit the use of resource pools, so another plan of mine, going forward, will be to include the logging in and out the machines in the process. This means in the scheduler the scheduler runs every 5 minutes. We are using Blue Prism Interact to load the queue, so the scheduler is set up like this
1. Login (Login Agent Process)
2. Process (Which can be a few seconds if there's no item)
3. Logout (Login Agent Process)
Now here is the problem. This schedule is setup similarly for many of our processes. This process, DumbSchedule, has it's runtime resource go offline at random times. The machine is not offline however the Automate.exe is not running (double checked by logging into the runtime resource and investigating). We also recently installed Dynatrace on some of our runtime resources to identify possible issues in our virtual environment. I noticed that the Automate.exe gets launched multiple times a day.
Through my previous work experiences we did not use a login agent, so the automate.exe file would only have to be launched once at bootup. Here it seems like it is launched multiple times. This leads me to some questions:
- Is this a best practice to launch it at login in every time? I googled the issue and from this thread it seems like it.
- Does logging off kill/close the Automate.exe? I don't see it in the object code, nor mentioned anywhere else, but I am not sure why the Automate.exe would not be running.