We have cases where our remote robots running from Orchestrator have a problem on the remote machine and something goes wrong, but the workflow remains running. We can tell by our log files in our database that our workflow has problems due to various data conditions (or lack of) and heartbeat updates that stop. We can also tell that the robot shows as still running in Orchestrator. When we find this condition we set a flag in our database that tells us that “Robot A” needs to be reset. As a result of this we want a workflow or .BAT file to be able to run on that remote robot (Robot A) and “reset” it. We have already built a workflow to “kill” all of our known processes on that remote machine and have figured out how to stop and start the robot so it will effectively reset. What we are trying to do is to run this “cleaner” workflow on the remote robot that is hung up in an automated manner. But we can’t get any process to run as the robot still shows the prior workflow running in Orchestrator.
Is anyone doing this, or something similar? I would to hear ideas from the community on how you are handling “hung” remote workflows which appear to be ok from the Orchestrator side.