08-03-19 12:30 PM
08-03-19 04:23 PM
10-03-19 09:31 PM
17-06-19 01:37 PM
Hej,
We also do bit of this, but you could encourage your ops team to do more than just ping.
Powershell and other tools can query the resource, but you need to query both login agent and runtime if you want to work on it to perfection.
http://<your.resouce.com>:8180/status <-- LoginAgent port. Runtime is normally 8181 if you did not change.
would respond something:
RESOURCE UNIT Total running: 0
The thing we did not figure out yet is how to cope with things like reboots, patch windows etc. "False positives"
BR,Håkan
02-08-19 06:51 AM
14-06-23 12:00 PM
To overcome these types of issues, I had created a task in task scheduler and this task will trigger PowerShell email script whenever the run time resource goes offline or connection lost state with the help of Blue Prism events.
Note: I had written PowerShell script for sending email.
14-06-23 02:41 PM
Sounds interesting. What is your input source here and how do you get to that?
14-06-23 02:57 PM
Input source would be your blue prism events (You can get these details from Event Viewer)
15-06-23 05:08 AM
Hi All,
I found an asset in DX which will trigger the automated email notification whenever a schedule didn't run due to resource unavailability or mis fired schedules. Has anyone tried this?