we have automated a couple of similar processes that basically download data from a web application and transfer them to a different machine by some ftp-tool. All of these unattended robots (each runs once a day) already worked fine for several days or weeks but since last week we occasionally encounter the following:
The robot is started by the orchestrator but then runs into an error, mostly when trying to grab the downloaded file, he catches this error and stops execution gracefully (we use RE Framework). Job status in Orchestrator is successful - so far, so good.
But any Job we start afterwards runs into an issue after a couple of activities, basically due to an activity timeout, these jobs also shut down gracefully and log status to orchestrator.
When I log in to the system where the unattended robot runs (with the robot user) I can see a couple of frozen application windows that have been started by the previous jobs and the robot executable remains frozen on the task bar. I cannot end any of these applications/processes. So we rebooted the whole system and everything ran fine again … but only for a couple of days, then the same happened again.
My suspicion was that at the time the robot ran, it was interrupted by some system update or OS shutdown signal. But according to IT at the time the robot ran there was no update, backup or similar going on.
Any idea what is going wrong here?